-
Bug
-
Resolution: Cannot Reproduce
-
P2
-
None
-
5.0u4
-
generic
-
solaris_2.4
Customer's application crashed about 3 to 5 hours into the run.
Looking at the crash core dump, its seems that GC thread 6113 gets a sig 11. Surprisingly the information of this thread is missing from hs_err log file.
The core file and error log files can be found at /net/oasis.west.sun.com/export/scratch/manish/customers/cisco/calls/830533
UC7_CP_JVMcrash_core.tar.gz core file
hs_err_pid5980.log hs_err file
aon_stdout.log_threaddump_before_test_CP thread dump before test starts
6113.txt ps auxw|grep 6113
You will notice from the core, that thread 6113 is the thread generating Seg11, from frame 8, siginfo struct.
hs_err file does not include thread 6113
but from threaddump taken before the test, you will find 6113 is second GC thread.
ps auxw|grep 6113 provides java GC thread is dead and in Zombie state.
Looking at the crash core dump, its seems that GC thread 6113 gets a sig 11. Surprisingly the information of this thread is missing from hs_err log file.
The core file and error log files can be found at /net/oasis.west.sun.com/export/scratch/manish/customers/cisco/calls/830533
UC7_CP_JVMcrash_core.tar.gz core file
hs_err_pid5980.log hs_err file
aon_stdout.log_threaddump_before_test_CP thread dump before test starts
6113.txt ps auxw|grep 6113
You will notice from the core, that thread 6113 is the thread generating Seg11, from frame 8, siginfo struct.
hs_err file does not include thread 6113
but from threaddump taken before the test, you will find 6113 is second GC thread.
ps auxw|grep 6113 provides java GC thread is dead and in Zombie state.