I can't say for sure that this is the cause of the behavior you're seeing,
but it's certainly something I'd recommend you fix. Keep in mind that the
heap is only part of the JVM's total RAM, and the JVM can only take part of
the host's RAM because the kernel needs some even if there aren't any othe
Thanks for the response Tim.
The logging has been enabled with "debug" level. :(
Still don't see that error.
mq is running with 16GB of JVM
*# Set jvm memory configuration (minimal/maximum amount of memory)
ACTIVEMQ_OPTS_MEMORY="-Xms8G -Xmx16G"*
[mule@lxp0172 kahadb]$ netstat -nap | grep 8161
I've seen Java processes that run out of heap hard-crash without logging
anything (sometimes they do, sometimes not, even from run to run). Could
you simply have used more heap than your JVM had available?
Do you get any additional useful logging at DEBUG or TRACE?
Tim
On Thu, Jul 20, 2017 at 12
