Hi, I can deadlock 5.1 & 5.2 latest snapshot configured for pure jdbc persistence using maven's performance test like this:
mvn activemq-perf:producer -Dfactory.brokerURL=tcp://192.168.228.84:61616 -Dproducer.sessTransacted=true -Dproducer.sessAckMode=transacted -Dproducer.deliveryMode=persistent -Dproducer.destName=queue://test.picaxu -DsysTest.reportName=all_transacted_producer mvn activemq-perf:consumer -Dfactory.brokerURL=tcp://192.168.228.84:61616 -Dconsumer.sessTransacted=true -Dconsumer.sessAckMode=transacted -Dconsumer.destName=queue://test.picaxu -DsysTest.reportName=all_transacted_consumer I've read what I've found on this (including AMQ-1606) but can't find a solution. I'm attaching my config, debug level logging & a thread dump during the deadlock. Any & all help appreciated. qvb -- pica http://www.nabble.com/file/p18117330/activemq.xml activemq.xml http://www.nabble.com/file/p18117330/thread.dump thread.dump http://www.nabble.com/file/p18117330/activemq.log activemq.log -- View this message in context: http://www.nabble.com/deadlock-on-memory-full-with-transacted-sends-tp18117330p18117330.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
