Hung Systems

If your system is hung, try to collect following information:

• Thread dump. A thread dump creates a stack trace for every running thread. Support can use thread dumps to determine the state of the system.

  To collect a thread dump, send a SIGQUIT signal to the Java process running Waveset, as follows:

  • In UNIX: Type kill -3 pid.

    Where pid is the process ID of the JVM running Waveset (usually the same as Application Server).

  • In Windows: Press CTRL-BREAK in the JVM console.

• Heap dump. A heap dump contains the entire status of what is in memory for a Java process.

  To force a heap dump, type the jmap -dump:file=filenamepid command.

  Where:

  • filename is the heap dump file to be created. Be aware that this file can be very large.

  • pid is the process ID of the JVM running Waveset (usually the same as Application Server).

• Screen shots or saved HTML pages. Use these tools to preserve information about the last action you performed before the system hung. You might capture information about the state of the system that is worth noting and saving for review.

• Recent activity report. If you can restart Waveset, you can retrieve an activity report that might help you determine what was happening in the system before the hang occurred.

  Select the Reports tab in Waveset; and generate a Recent Systems Messages report and a Today's Activities report.