[
http://jira.jboss.com/jira/browse/JBTM-218?page=all ]
Phillip Thurmond reopened JBTM-218:
-----------------------------------
Sorry Mark, I mis-typed. I meant to say that the object should probably be changed to
ConcurrentHashMap. Whenever a hashtable is accessed, the whole object must be locked.
Using ConcurrentHashMap, only a portion of the object is locked, so the contention will be
reduced.
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
Fix For: 4.2.3.SP3
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