Java Troubleshooting Guide for HP-UX Systems

- waiting on <11000100> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:133)
- locked <11000100> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:149)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:197)
"Reference Handler" daemon prio=10 tid=0052de80 nid=12 lwp_id=2669767 in Object.wait() [752c0000..752c0ce0]
at java.lang.Object.wait(Native Method)
- waiting on <11003dc8> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:123)
- locked <11003dc8> (a java.lang.ref.Reference$Lock)
"main" prio=8 tid=0047dc90 nid=1 lwp_id=-1 waiting on condition [7fffd000..7fffe398]
at java.lang.Thread.sleep(Native Method)
at spec.jbb.JBButil.SecondsToSleep(JBButil.java:740)
at spec.jbb.Company.displayResultTotals(Company.java:942)
at spec.jbb.JBBmain.DoARun(JBBmain.java:387)
at spec.jbb.JBBmain.DOIT(JBBmain.java:1137)
at spec.jbb.JBBmain.main(JBBmain.java:1490)
"VM Thread" prio=10 tid=004ff510 nid=11 lwp_id=2669766 runnable
"GC task thread#0 (ParallelGC)" prio=10 tid=004d0520 nid=3 lwp_id=2669758 runnable
"GC task thread#1 (ParallelGC)" prio=10 tid=004d0600 nid=4 lwp_id=2669759 runnable
"GC task thread#2 (ParallelGC)" prio=10 tid=004d06e0 nid=5 lwp_id=2669760 runnable
"GC task thread#3 (ParallelGC)"prio=10 tid=004d07c0 nid=6 lwp_id=2669761 runnable
"GC task thread#4 (ParallelGC)" prio=10 tid=004d08a0 nid=7 lwp_id=2669762 runnable
"GC task thread#5 (ParallelGC)" prio=10 tid=004d0980 nid=8 lwp_id=2669763 runnable
"GC task thread#6 (ParallelGC)" prio=10 tid=004d0a60 nid=9 lwp_id=2669764 runnable
"GC task thread#7 (ParallelGC)" prio=10 tid=004d0b40 nid=10 lwp_id=2669765 runnable
"VM Periodic Task Thread" prio=8 tid=00500ad0 nid=18 lwp_id=2669773 waiting on condition
1.3 Fatal Error Log (hs_err_pid<pid>.log)
When a fatal error occurs, an error log is created in the file hs_err_pid<pid>.log, where
<pid> is the process id of the process. The file is created in the working directory of the process,
if possible. In the event that the file cannot be created in the working directory (for example, if
there is insufficient space, a permission problem, or another issue), then the file is created in the
temporary directory, /tmp. The error log contains information obtained at the time of the fatal
error. This includes :
• Operating exception or signal that provoked the fatal error
• Version and configuration information
• Details on the thread that provoked the fatal error and its stack trace
• List of running threads and their states
• Summary information about the heap
• List of native libraries loaded
• Command-line arguments
• Environment variables
• Details about the operating system and processor
In some cases, only a subset of this information is output to the error log. This happens when a
fatal error is so severe that the error handler is unable to recover and report all details.
1.4 gcore
The gcore command creates a core image of a running process. By default, the name of the core
file for a process-id will be core.process-id. The process information in the core image
can be obtained by using gdb or other debuggers. The usage of gcore is:
gcore [-o prefix] <pid> [pid ....]
When gcore creates a core image of each specified process, the process is temporarily stopped.
When the creation of the core image is complete, the process continues to execute.
18 Diagnostic and Monitoring Tools and Options