[
http://jira.jboss.com/jira/browse/JBTM-218?page=comments#action_12361999 ]
Mark Little commented on JBTM-218:
----------------------------------
As with 216, this is called whenever a thread needs to get the currently associated
transaction (which could be an imported transaction, a deeply nested transaction etc.) The
transaction has multiple representations in JBossTS: JTA, core, JTS and WS-T. In this
case, obviously it's just JTA and core, but we need to do a mapping from one to the
other, which is what's happening here. It needs to be synchronized on all accesses.
Contention on HashTable in
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.java
---------------------------------------------------------------------------------------------------
Key: JBTM-218
URL:
http://jira.jboss.com/jira/browse/JBTM-218
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.3
Reporter: Phillip Thurmond
Assigned To: Mark Little
I'm seeing some contention on the object _transactions in the class
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple. Most of the
contention happens in the getTransaction() method.
--
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