You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by pica <pi...@biaix.org> on 2008/06/25 20:32:59 UTC
deadlock on memory full with transacted sends
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.
Re: deadlock on memory full with transacted sends
Posted by pica <pi...@biaix.org>.
Hi,
I've tried it with no luck. I've read about prefetchlimit, flowcontrol &
friends, but I'm having trouble making sense of it all. I'm developing and
invoicing application with camel, and thus I require reliable rather than
fast messaging (i.e.: HA, persistent messages, XA transactions and all the
fun). Apparently ActiveMQ is tuned out-of-the box for precisely the
opposite. What are the most relevant configuration options I should play
with?
thanks
--
pica
rajdavies wrote:
>
> Can you try setting your memory limit much higher? i.e. in your config
> change - <memoryUsage limit="10 mb" percentUsageMinDelta="20"/> to
> <memoryUsage limit="100 mb" percentUsageMinDelta="20"/>
>
> cheers,
>
> Rob Davies
> 'Go further faster with Apache Camel!'
> http://rajdavies.blogspot.com/
>
> On 25 Jun 2008, at 19:32, pica wrote:
>
>>
>> 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.
>>
>
>
>
>
>
>
>
>
>
--
View this message in context: http://www.nabble.com/deadlock-on-memory-full-with-transacted-sends-tp18117330p18131925.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: deadlock on memory full with transacted sends
Posted by Rob Davies <ra...@gmail.com>.
Can you try setting your memory limit much higher? i.e. in your config
change - <memoryUsage limit="10 mb" percentUsageMinDelta="20"/> to
<memoryUsage limit="100 mb" percentUsageMinDelta="20"/>
cheers,
Rob Davies
'Go further faster with Apache Camel!'
http://rajdavies.blogspot.com/
On 25 Jun 2008, at 19:32, pica wrote:
>
> 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.
>