|
||||||||
|
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 |
||||||||
So I think thread comparisons ought to be how this is handled. The danger to Hibernate is exactly the concurrency introduced by the sync callbacks from different threads so thats what we really need to protect against.
On JBoss at least, using the Thread id is supposedly enough given this use case.
I think that both the clear and exception (if we opt to throw exception - and I vote we should) should be delayed and performed from the main thread via the session method call hooks discussed elsewhere.