JTA synchronisation warning
----------------------------
Key: NXP-2811
URL: http://jira.nuxeo.org/browse/NXP-2811
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.2 M3
Since DocumentManagerBean implements SessionSynchronization we can see multiple
warning in the logs each time the DocumentManagerBean gets released :
TwoPhaseCoordinator.afterCompletion - returned failure ....
This WARNING is caused because the JTA Synchronizer registred by the Jboss
SessionSynchronizationInterceptor try to call afterComplete method on the bean
just after the RemoveInterceptor terminated the bean.
This is caused by 2 JBoss bugs :
1 - since JTA spec does not really allow to order the synchronizer there is no
way to be sure the Remove synchronizer will be called after the Session
synchronizer
Actually, the arjuna implementation stored synchronizer in a set that is
ordered by the dynamically generated UUID ....
2 - the JBoss interceptor that register the Session Synchronizer has a bug : it
register the synchronizer each time a method of the bean is called
=> since arjuna has no way to detects that the synchronizer is the same
(dynamically generated UUID) the synchronizer stack is filled with plenty of
SessionSynchronisers
=> it gives fewer chances to have the synchronizer properly ordered
=> this make the warn being displayed several times
=> this is bad for perfs
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
