[jboss-jira] [JBoss JIRA] Closed: (JBTM-218) Contention on HashTable in com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.java
Mark Little (JIRA)
jira-events at lists.jboss.org
Thu May 10 14:12:02 EDT 2007
[ http://jira.jboss.com/jira/browse/JBTM-218?page=all ]
Mark Little closed JBTM-218.
----------------------------
Fix Version/s: 4.2.3.SP3
Resolution: Rejected
The datastructure needs to be synchronized on all accesses. A given thread may call this operation (indirectly) many times during the coure of a transaction. Given the nature of what is stored (transactions) a hash approach makes much more sense that any other structure. Hashtable versus synchronized HashMap doesn't offer significant performance benefits as far as I can see.
> 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
More information about the jboss-jira
mailing list