Alan Conway created QPID-5720:
---------------------------------

             Summary: HA exception raised by the store for durable transactions
                 Key: QPID-5720
                 URL: https://issues.apache.org/jira/browse/QPID-5720
             Project: Qpid
          Issue Type: Bug
          Components: C++ Clustering
            Reporter: Alan Conway
            Assignee: Alan Conway


Description of problem:
While playing with the new cluster implementation, I came across the following 
problem. When the qpid-txtest tool is executed with "--durable yes --transfer 
yes" options (that is, the journal is used on the brokers and messages are 
transferred from one queue to another), the journal on the broker raises an 
exception:

[root@mrg-qe-11 ~]# /usr/libexec/qpid/tests/qpid-txtest --init yes --transfer 
yes --check yes --durable yes --broker 192.168.101.251
Transfering from tx-test-1 to tx-test-2
Transfering from tx-test-2 to tx-test-1
Drained 9 messages from tx-test-1
2014-04-15 07:53:16 [Client] warning Broker closed connection: 320, Queue 
tx-test-2: async_dequeue() failed: jexception 0x0b02 wmgr::dequeue_check() 
threw JERR_MAP_LOCKED: Record ID locked by a pending transaction. (drid=0xb) 
(/builddir/build/BUILD/qpid-0.22/cpp/src/qpid/linearstore/MessageStoreImpl.cpp:1268)
Queue tx-test-2: async_dequeue() failed: jexception 0x0b02 
wmgr::dequeue_check() threw JERR_MAP_LOCKED: Record ID locked by a pending 
transaction. (drid=0xb) 
(/builddir/build/BUILD/qpid-0.22/cpp/src/qpid/linearstore/MessageStoreImpl.cpp:1268)

Version-Release number of selected component (if applicable):
qpid-cpp-0.22-37.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Configure and start HA cluster.
2. Execute qpid-txtest tool with "--durable yes --transfer yes" options.
3.

Actual results:
journal exception is raised.

Expected results:
No exception.




--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to