Since you seem to want to go out of your way to identify this as a Hibernate bug, not a Terracotta bug once and for all, I should point out that these are classes actually maintained in the Hibernate code base by Terracotta developers
That being said, I will have to talk to them since I really am not sure why this code is written the way it is and given that there are no tests that test it I cannot even trigger the condition you see...
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
Since you seem to want to go out of your way to identify this as a Hibernate bug, not a Terracotta bug once and for all, I should point out that these are classes actually maintained in the Hibernate code base by Terracotta developers
That being said, I will have to talk to them since I really am not sure why this code is written the way it is and given that there are no tests that test it I cannot even trigger the condition you see...