Are you sure it is crashing and not simply just shutting down? You never said if there was anything in the serve log about a shutdown. If it is crashing, then it is the JVM that is crashing. What OS are you running? Have you updated any system files lately? The 1.5.0_06 JVM is very old and might not behave well with up-to-date system libraries (I would not run that old of a version on Windows Server 2008, for example). Try upgrading to the latest 1.5.0 JVM and see if that fixes the problem.
Hi Peter ,
We are running the jboss in a Linux os RHEL 4.
There is no details in the server log about the shutdown
I didn't find any JVM crash logs for the pid in the server.
Is it possible to make jboss log the details about the crash ?
>>Is it possible to make jboss log the details about the crash ?
No, because the JVM is crashing.
>>There is no details in the server log about the shutdown
Does this mean that there was no shutdown information at all, or that there was shutdown information but nothing to indicate a cause???
>>Does this mean that there was no shutdown information at all, or that there was shutdown information but nothing to indicate a cause???
There is no shutdown information at all .I have set up monitoring for memory usage to see whether it is related to memory[There was no Out Of Memory Errors].
and also for active threads .But they all look fine
OK, then you do have a JVM crash so the link that Wolf-Dieter provided won't help. It probably is not a Java out-of-memory error because those are caught and logged by JBoss AS.
Are you starting JBoss AS from an init.d script? If so, does the script redirect stdout/stderr? If so, is there any info in that file? Could you run JBoss AS manually from a command line instead and see if you get any extra info (on Windows, when the JVM crashes, it displays a dialog box, but that happens only when running from a command line). It is also very possible that since the JVM intercepts crash information and displays it before it shuts down, there there will be no standard OS crash dump file. (That is just a guess, I haven't had a JVM crash in Linux for a long time and I don't recall what I did.)
we are running the jboss from command line.
These are our startup parameters
/opt/jdk1.5.0_06/bin/java -Djava.rmi.server.hostname=X.X.X.X -Djboss.bind.address=X.X.X.X -server -Xms1024m -Xmx2048m -Xloggc:ecperf.gc.log -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -XX:+UseConcMarkSweepGC -XX:+CMSPermGenSweepingEnabled -XX:+CMSClassUnloadingEnabled -XX:PermSize=128m -XX:MaxPermSize=256m -Dprogram.name=run.sh -DJBA_CONFIG=/opt/config -Dprogram.name=run.sh -DAS_LOG=/opt/log -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=6789 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dprogram.name=run.sh -Djava.endorsed.dirs=/opt/jboss-4.0.4/lib/endorsed -classpath /opt/jboss-4.0.4/bin/run.jar:/opt/jdk1.5.0_06/lib/tools.jar org.jboss.Main -b X.X.X.X
Since you didn't mention it, can I assume that you are not seeing anything crash-related in the terminal used to start JBoss AS?
I think that your next step is to get the most recent version of JVM 1.5.
yes we dont see anything in the terminal.ok will recent version of JVM 1.5
If JVM update doesn't help ... maybe use the most recent 1.6
Do you see any hs_err_pid*.log files in the directory where you start via command line.
Maybe change the run script to catch the signals and echo the exit status of JVM and the timestamp helps.
There is no hs_err_pid*.log file created .
Do i need to provide any parameters to VM in start up to generate this log file during the crash?
If there was a crash, the fatal error log should always be created. See this for details on where the fatal error log goes:
If the fatal error log is not created, and there is nothing in the JBoss AS server log to indicate a shutdown, then something else is going on.