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 other user processes. On a 16GB host, if nothing else is running there, 12GB of heap would be very safe, 14GB should work, and 15GB might work. But I'd start with 12GB and see if your crashing behavior disappears, and you can consider whether to increase the value later.
Tim On Jul 20, 2017 1:09 AM, "Prashant Katti" <kattiprash...@gmail.com> wrote: > 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 > (Not all processes could be identified, non-owned process info > will not be shown, you would have to be root to see it all.) > tcp6 0 0 :::8161 :::* LISTEN > 59849/java > *[mule@lxp0172 kahadb]$ ps -ef | grep 59849 > mule 59849 1 4 Jul19 ? 00:10:28 /app/jdk1.8.0_91/bin/java > -Xms8G -Xmx16G * > > > and total memory on system is > > *[mule@lxp0172 bin]$ cat /proc/meminfo > MemTotal: 16260324 kB* > MemFree: 670892 kB > MemAvailable: 7691660 kB > > Is this causing any issue? > > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Activemq-Master-dying-without-errors-tp4728716p4728720.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
