[
http://jira.jboss.com/jira/browse/JBMESSAGING-660?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-660:
-------------------------------------
I have fixed this by executing the cancel on the queue's event queue. This means we do
not get a knock on deadlock and don't need to copy any deliveries in the server
consumer endpoint.
I have also strengthened checking and handling of ack/cancels/commits when session is
closed - as this was giving a separate problem.
I have also implemented jdbc deadlock retry on all db updates rather than just one which
we were previously doing.
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