This topic comes up quite often. If you search the forums you might find some hints as to what to do. Here are two recent discussions to get you started.
However our log files do not mention the word shutdown. The log file just stops being written to, until jboss restarts.
We have increased the memory allocation, and fingers crossed it helps.
Otherwise, I have found this from a pdf "JBossProfiler Guide.pdf";
3.2. Capturing a Snapshot
Steps to extract a snapshot:
- Add jbossAgent.dll to your path or libjbossAgent.so to your LD_LIBRARY_PATH
- Add -agentlib:jbossAgent to your JVM 5 command line. (Java 5 at least is required as JVMTI was introduced on
- Go to JMX Console (http://localhost:8080/jmx-console) and look for JBossProfiler:JVMTI MBean
- Call heapSnapshot from JVMTIClass MBean. use P1 as a prefix, and P2 as the extension. For instance
P1=/tmp/log, and P2=mem. This will create three files starting with log under /tmp, with extension=.mem
- Use the JbossProfiler application (http://localhost:8080/jboss-profiler) after you have installed jboss-profiler.war
to your /deploy directory.
The log file just stops being written to, until jboss restarts.
This sounds like either a JVM crash, or the OS is forcibly terminating the process (e.g., kill -9 on Linux or End Process in Task Manager on Windows). For the former, a process dump file might be present. For the later, you might have to dig through OS config settings to see if there is something, such as a scheduled task, that is killing the process.