Hi Gordon, I was stopping the application that was dead-locked; after unsuccessful attempt I just killed -9 it. So the app was killed when the transaction was in progress. After that I just restarted the application and "Record ID locked by a pending transaction" started to appear.
>> Are you using XA? If so the transaction manager may offer tools to list >> transactions. You can do it using AMQP 0-10 directly, but not through the >> recommended APIs. Worst case I could give you a little script. We are using local transactions only. Best Regards, Sergey Zhemzhitsky -----Original Message----- From: Gordon Sim [mailto:g...@redhat.com] Sent: Monday, September 09, 2013 8:07 PM To: users@qpid.apache.org Subject: Re: Manually aborting a pending transaction On 09/09/2013 02:42 PM, Zhemzhitsky Sergey wrote: > HI qpid gurus, > > Recently we have faced with following exception > > 2013-09-09 17:38:23,874 | ERROR | IoReceiver - > locahost/10.20.26.150:5672 | > org.apache.qpid.client.AMQConnectionDelegate_0_10 | | 217 - qpid - > 0.18.0.1 | connection exception: conn:21aa419a > org.apache.qpid.transport.ConnectionException: Queue test_queue: > async_dequeue() failed: jexception 0x0b02 wmgr::dequeue_check() threw > JERR_MAP_LOCKED: Record ID locked by a pending transaction. (drid=0xde12a) > (MessageStoreImpl.cpp:1419) > at > org.apache.qpid.transport.Connection.closeCode(Connection.java:531)[217:qpid:0.18.0.1] > at > org.apache.qpid.transport.ConnectionDelegate.connectionClose(ConnectionDelegate.java:75)[217:qpid:0.18.0.1] > at > org.apache.qpid.transport.ConnectionDelegate.connectionClose(ConnectionDelegate.java:40)[217:qpid:0.18.0.1] > at > org.apache.qpid.transport.ConnectionClose.dispatch(ConnectionClose.java:91)[217:qpid:0.18.0.1] > at > org.apache.qpid.transport.ConnectionDelegate.control(ConnectionDelegate.java:49)[217:qpid:0.18.0.1] > at > org.apache.qpid.transport.ConnectionDelegate.control(ConnectionDelegate.java:40)[217:qpid:0.18.0.1] > at > org.apache.qpid.transport.Method.delegate(Method.java:163)[217:qpid:0.18.0.1] > at > org.apache.qpid.transport.Connection.received(Connection.java:376)[217 > :qpid:0.18.0.1] > Do you know whether this happens after failover or not? (One possible cause I can come up with is around confusion over message identifiers which could in theory happen after a failover). --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org _______________________________________________________ CONFIDENTIALITY NOTICE: This email and any files attached to it may be confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
