In the case of a closed session a new session is temporarily opened because it has to be. In the case of a cleared session, the session is still open and still known to the lazy entity/collection, so that session (and any transactional context) is used. Still does not explain why the locks are not released when the session is ultimately closed (and the transaction is committed).
Not sure what you mean by "the other 2 close them first". The other 2 what?
Again, what kind of lock are showing up in pg_locks here?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
In the case of a closed session a new session is temporarily opened because it has to be. In the case of a cleared session, the session is still open and still known to the lazy entity/collection, so that session (and any transactional context) is used. Still does not explain why the locks are not released when the session is ultimately closed (and the transaction is committed).
Not sure what you mean by "the other 2 close them first". The other 2 what?
Again, what kind of lock are showing up in pg_locks here?