[jbossts-issues] [JBoss JIRA] Commented: (JBTM-365) addSynchronization calls during beforeCompletion are problematic
Steven Hawkins (JIRA)
jira-events at lists.jboss.org
Mon May 19 13:08:59 EDT 2008
[ http://jira.jboss.com/jira/browse/JBTM-365?page=comments#action_12413247 ]
Steven Hawkins commented on JBTM-365:
-------------------------------------
The defect is that normal commit is failing due to an ill-timed call to addSynchronization. Is there a reason why we as a client would need explicit synchronization to calls to addSynchronization? Our integration of JBossTS does have separate threads calling addSynchronization and that may actually be committing. However isn't this a general concurrency problem since beforeCompletion may also be initiated asynchronously wrt addSynchronization during a timeout.
> addSynchronization calls during beforeCompletion are problematic
> ----------------------------------------------------------------
>
> Key: JBTM-365
> URL: http://jira.jboss.com/jira/browse/JBTM-365
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA Implementation
> Affects Versions: 4.3.0.GA
> Reporter: Steven Hawkins
>
> Asynch calls to com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.addSynchronization during beforeCompletion are problematic since access to _currentRecord and _synchs is unsynchronized in addSynchronization wrt beforeCompletion. This is similar to JBTM-188.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues
mailing list