PQ74570: SIGSEGV IN LIBXHPI.A WHEN GENERATING A JAVACORE (IN A DGGENERATEJAVACORE METHOD). | |||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description An AppServer or AdminServer jvm crashes with a SIGSEGV in libxhpi.a. The native call stack shows that the jdk is in the middle of generating a javacore, meaning that it is already processing a signal (such as SIGSEGV, SIGQUIT, SIGILL). . Problem Summary: The jdk crashed during signal handling of a prior signal. The stack trace for the thread that catches the exception is The stdout file will show something like this:Local fix To get to the underlying exception that causes the javacore processing to start, set the environment variable DISABLE_JAVADUMP=true This prevents the javacore processing from being done by the Java signal handler. This will produce the core file or user.dmp file (on Windows) that can be formatted so that you can view the root exception. . JVMXM004: JVM is performing abort shutdown sequence JVMDG217: Dump Handler is Processing a Signal - Please Wait. JVMDG303: JVM Requesting Java core file JVMDG304: Java core file written to /DWL/Customer35/CInstance01/properties/javacore6450.1051128955.t JVMDG215: Dump Handler has Processed Exception Signal 11." . The javacore files show that an exception is occuring during the exception: 3XHNATIVESTACK Native Stack NULL ------------ 3XHSTACKLINE at 0xD22FC010 in DumpInitialDetails 3XHSTACKLINE at 0xD22FBBB8 in Diagnostics 3XHSTACKLINE at 0xD3FD8F98 in dgGenerateJavacore 3XHSTACKLINE at 0xD3FD7610 in dgDumpHandler 3XHSTACKLINE at 0xD3FDB014 in abortJVM 3XHSTACKLINE at 0xD3FDA914 in panicSignalHandler . Problem Conclusion: This is SOV defect, 57168. The specific jdk that resolves this problem is the ca131-20021218 build. . A jdk upgrade to ca131-20030412 will fix this problem.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * using jdk prior to ca131-20030412. * **************************************************************** * PROBLEM DESCRIPTION: SIGSEGV in libxhpi.a when generating * * a javacore (in a degeneratejavacore * * method. * **************************************************************** * RECOMMENDATION: * **************************************************************** An AppServer or AdminServer jvm crashes with a SIGSEGV in libxhpi.a. The native call stack shows that the jdk is in the middle of generating a javacore, meaning that it is already processing a signal (such as SIGSEGV, SIGQUIT, SIGILL). The jdk crashed during signal handling of a prior signal.Problem conclusion A jdk upgrade to ca131-20030412 will fix this problem.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ74570
IBM Group: Software Group
Modified date: May 28, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.