-
Notifications
You must be signed in to change notification settings - Fork 38.1k
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
hibernate isolation property release_mode
-> on_close not working
#32556
Comments
Thanks for getting in touch, but it feels like this is a question that would be better suited to Stack Overflow. As mentioned in the guidelines for contributing, we prefer to use the issue tracker only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add some more details if you feel this is a genuine bug. |
@snicoll Thanks for your response. Upon further examination, I discovered that when the JTA configuration is set for
|
When migrating from the existing Spring Boot version
2.4.1 to 3.2.4
, I encountered a question. When the following property is defined in hibernate-core(? or hibernate-orm) (Spring Boot version 2.4.1), it seems to be applied correctly:spring.jpa.properties.hibernate.connection.release_mode=on_close
However, when using Hibernate-core version
6.2.3.Final
in version3.2.4
(starting from the minimum version supporting 3.x
), this option is not applied, and it continues to be applied as after_statement. If I need to override the isolation property of the@Transactional
annotation, the error occurs as follows becausesession.getJdbcCoordinator().getLogicalConnection().getConnectionHandlingMode().getReleaseMode()
at line 92 ofHibernateJpaDialect.class
is notON_CLOSE
:Additionally, I have tested setting the value declared in
PhysicalConnectionHandlingMode.class
,DELAYED_ACQUISITION_AND_HOLD
, asspring.jpa.properties.hibernate.connection.handling_mode=DELAYED_ACQUISITION_AND_HOLD
, but the same error occurs. Is it not possible for users to control this value in the latest version? If not, could you please provide specific guidance on why this is not possible, who is responsible for calling this option, and any alternative solutions? If all of the above is an issue with the current version, I would like to request a fix.The text was updated successfully, but these errors were encountered: