|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
It's going to be resolved in 4.1.7 for sure. Could you please submit entity mapping and sequence of JPA operations that cause such exception? Does it have to do something with second level cache? I want to make sure that it will not happen again.