I created an issue for this in the ActiveMQ JIRA:
https://issues.apache.org/activemq/browse/AMQ-1503
--
View this message in context:
http://www.nabble.com/Out-of-memory-error-with-durable-subscribers-tf4487985s2354.html#a13959856
Sent from the ActiveMQ - User mailing list archive at Nabble.com
We did not do a jvm kill -3, we got the OOME on the broker. We were able to
send more messages because we pushed the memory size to 1024M for jvm, 512M
for broker to allow more time for the check point to occur (we were guessing
that was the issue, but it was not).
BTW we are using AMQ version
Mike,
Are you getting OOMEs on the publisher (the client) or in the broker?
I'm wondering if you can send your jvm a kill -3 signal to get a
thread dump, because it sounds vaguely like the problem that I'm
currently experiencing. However, my publishers can only send ~1390
messages before
Is there any chance someone from the ActiveMQ team can give some insiders
feedback on the below? Even if it's 'durable subscribers are unstable -
don't use them'?
Thanks,
Mike Roberts (development manager for the team Ahmed is on)
aselshamy wrote:
>
> Hi
>
> We have one topic publisher that
