[jbossts-issues] [JBoss JIRA] (JBTM-1840) Incorrect handling of multi-threaded access to JCA connections
Eytan David (JIRA)
jira-events at lists.jboss.org
Sun Jul 14 11:54:26 EDT 2013
Eytan David created JBTM-1840:
Summary: Incorrect handling of multi-threaded access to JCA connections
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.Final
Environment: Red Hat Linux, Jboss EAP 6.0
Reporter: Eytan David
Assignee: Tom Jenkinson
The issue JBPAPP-5596 which according to the documentation should have been resolved in Jboss EAP 5.1.1, still occurs in EAP 6.0
The case describes a situation in which a long transaction (in a service handled by JTA) is set to be rolled back, but gets into a dead lock with the reaper thread.
Deadlock as described in the stack trace:
Found one Java-level deadlock:
waiting for ownable synchronizer 0xb22a2e58, (a java.util.concurrent.locks.ReentrantLock$NonfairSync),
which is held by "http-127.0.0.1-8080-1"
waiting to lock monitor 0x4e200ef4 (object 0xaa937ab0, a com.arjuna.ats.internal.jta.transaction.arjunacore.AtomicAction),
which is held by "Thread-20"
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues