Community
Participate
Working Groups
If you have exclusive-connection.mode = Always, then read-only queries can leak connections. The issue is a ClientSession is created, but never released. JPA needs to release the client session. Also ServerSession executeQuery acquires a ClientSession and never releases it. Fix will hold readOnlySession in EntityManagerImpl and release on close.
Ref Oracle bug#13690092
SVN trunk commit: Bug#370855 exclusive connection leaking https://bugs.eclipse.org/bugs/show_bug.cgi?id=370855 Fixes issue with exclusive-connection.mode Always and read-only queries leaking connections. Code review: Andrei Changes: - Added readOnlySession to EntityManagerImpl to hold read-only ClientSession to ensure it is released on close. - Fixed ServerSession to release ClientSession allocated for query execution. - Fixed batch writing logging to log with correct connection id.
Created attachment 210673 [details] patch
fixed
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink