Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for configuration of both primary and secondary db connection pool #439

Merged
merged 2 commits into from
Dec 5, 2022

Conversation

nscuro
Copy link
Collaborator

@nscuro nscuro commented Dec 4, 2022

Instead of implicitly applying the same property values for both pool types.

See DependencyTrack/dependency-track#1935 for context.

This PR introduces new config keys for both the primary (transactional, tx) and secondary (*non-transactional, nontx) connection pools, all which default to null and fall back to the existing pool config keys to remain backward compatible.

Instead of implicitly applying the same property values for both pool types.

Signed-off-by: nscuro <[email protected]>
@stevespringett stevespringett merged commit ad9e269 into stevespringett:master Dec 5, 2022
@nscuro nscuro deleted the connection-pooling branch December 5, 2022 11:55
nscuro added a commit to nscuro/Alpine that referenced this pull request May 1, 2024
As reported via DependencyTrack/dependency-track#1987

This appears to be a regression introduced via stevespringett#439.

Signed-off-by: nscuro <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants