Last week I was monitoring a JBOSS environment on a linux server (Red Hat Enterprise Linux AS release 4 (Nahant Update 4)) using jconsole as the monitoring tool. I was running jconsole from my windows box. JAVA_HOME on the server side is java 1.6. The jconsole I was using on my windows box is also java 1.6. All was well, the memory was fine and all seemed to be going smoothly so I was ready to head home. I did not close jconsole out or anything I just shut my laptop. A few minutes later I'm notified that the server I was monitoring was down (A production environment). I check the logs on the database and the server.log on Jboss and cannot see anything that would indicate a problem. All I see is that jboss stopped. No errors or anything.
Basically I'm trying to see if closing down jconsole causes jboss to crash? That is the only theory I can come up with. Here are my setting in the run.conf file on the jboss server side:
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms3072m -Xmx3072m -XX:MaxPermSize=256m -DdebugMode=true -DrunQuartz=all -Dsun.lang.ClassLoader.allowArraySyntax=true"
# Set the garbage collection options
JAVA_OPTS="$JAVA_OPTS -XX:+UseConcMarkSweepGC -XX:+PrintTenuringDistribution -XX:+PrintGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Dsun.rmi.dgc.client.gcInterval=21600000 -Dsun.rmi.dgc.server.gcInterval=21600000"
#if you want to log garbage collection uncomment the next line
# enable JConsole remote port
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=12000 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"
# Set the tmp directory location
# Sample JPDA settings for remote socket debuging
# Sample JPDA settings for shared memory debugging
I'm having a hard time trying to find out what could be the problem. Any advice or additional information needed let me know.