Skip to content

Avoid internal lifecycle synchronization for SingleConnectionFactory and SingleConnectionDataSource #32284

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.

Sign up for GitHub

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

Jump to bottom
Closed
jhoeller opened this issue Feb 16, 2024 · 0 comments
Closed

Avoid internal lifecycle synchronization for SingleConnectionFactory and SingleConnectionDataSource #32284

jhoeller opened this issue Feb 16, 2024 · 0 comments
Assignees
@jhoeller
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) in: messaging Issues in messaging modules (jms, messaging) type: enhancement A general enhancement
Milestone
6.2.0-M1

Comments

@jhoeller
Copy link
Contributor

Along with #32252, it turns out that the JMS SingleConnectionFactory and also the JDBC SingleConnectionDataSource should also benefit from a synchronization-free lifecycle lock arrangement for startup/shutdown.
@jhoeller jhoeller added in: messaging Issues in messaging modules (jms, messaging) in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement labels Feb 16, 2024
@jhoeller jhoeller added this to the 6.2.0-M1 milestone Feb 16, 2024
@jhoeller jhoeller self-assigned this Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhoeller jhoeller

Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) in: messaging Issues in messaging modules (jms, messaging) type: enhancement A general enhancement
Projects
None yet
Milestone
6.2.0-M1
Development

No branches or pull requests
1 participant
@jhoeller