[
http://jira.jboss.com/jira/browse/JBMESSAGING-660?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-660:
---------------------------------------------
When I run the test I get an eventual dead lock.
I have attached a trace...
The object lock from ChannelSupport and the object lock from ServerConsumerEndpoint are
bouncing with each other. Look at trace.txt (attached) for more details.
"Thread-42" prio=1 tid=0x08269c00 nid=0x2a49 waiting for monitor entry
[0x695d6000..0x695d71b0]
at
org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:223)
- waiting to lock <0xafb81b30> (a java.lang.Object)
at
org.jboss.messaging.core.local.RoundRobinPointToPointRouter.handle(RoundRobinPointToPointRouter.java:110)
at org.jboss.messaging.core.ChannelSupport.push(ChannelSupport.java:1652)
at
org.jboss.messaging.core.ChannelSupport.deliverInternal(ChannelSupport.java:703)
- locked <0x7175c310> (a java.lang.Object)
at
org.jboss.messaging.core.ChannelSupport$DeliveryRunnable.run(ChannelSupport.java:1695)
at
EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:595)
Race Condition Between Session.close and Session.commit or
Session.rollback
---------------------------------------------------------------------------
Key: JBMESSAGING-660
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-660
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.0.1.GA
Reporter: Clebert Suconic
Assigned To: Ovidiu Feodorov
Fix For: 1.0.1.SP2
Attachments: race.log, trace.txt
--
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