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
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
At the time of the out of memory, one of the
