|
||||||||
|
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 |
||||||||
I think that the impact of the "possible non-threadsafe access to the session" AssertionFailure, is that the application gets an error that is not easily understood (but the JTA transaction is also rolled back as expected). If the application thread wasn't in the middle of an EntityManager invocation, we still would want to call the equivalent of EntityManager.clear() from the reaper TX AfterCompletion callback (to remove updated/loaded entities from the persistence context).
Since the JTA transaction is rolling back as part of the timeout, the application probably only expects to see an error exception about the transaction rolling back. The application doesn't expect the AssertionFailure (IMO).