That is very strange. What kind of locks are you seeing?
The only thing I can think of there is that the "special Sessions" obtained during testLazyCollectionLoadingWithClearedSession are not being released (closed) in a way that signals to the driver to release its locks. Maybe because we do not do anything at all with transactions on those "special Sessions"? We should find out from #postgresql what exactly happens in the case of un-finished transactions from the JDBC driver.
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
That is very strange. What kind of locks are you seeing?
The only thing I can think of there is that the "special Sessions" obtained during testLazyCollectionLoadingWithClearedSession are not being released (closed) in a way that signals to the driver to release its locks. Maybe because we do not do anything at all with transactions on those "special Sessions"? We should find out from #postgresql what exactly happens in the case of un-finished transactions from the JDBC driver.