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 getting an OOME with a 64Mb heap.
phil.
On Oct 1, 2007, at 1:33 PM, mikebroberts wrote:
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 publish 2M messages with 4 durable
subscribers. Things go fine till we reached 1.7M we get the
outofmemoryerror.
AMQ is setup to use 5 * 20M log files, and derbydb jdbc
persistence. It
starts with -Xmx1024M and <usageManager id="memory-manager"
limit="512
MB"/>
At the time of the out of memory, one of the log file is gone
crazy and
it's size is 415M, derbydb size is so big as well.
We are using session client acknowledgment. and prefetch size of
1 (we
need to serialize message consumption).
each message is being acknowledged using
javax.jms.Message.acknowledge();
did not find anything on how to change checkpoint interval for
persistence.
Any thoughts on what could be the issue?
--
View this message in context: http://www.nabble.com/Out-of-memory-
error-with-durable-subscribers-tf4487985s2354.html#a12983727
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Whirlycott
Philip Jacob
[EMAIL PROTECTED]
http://www.whirlycott.com/phil/
