PQ74194: SIGABRT IN /USR/LIB/LIBPTHREADS.A. THE JDK IS IN A _JIT_NEWARRAY CALL WHEN THIS OCCURS.

 A fix is available

***SUPERCEDED*** 1.3.1 Java SDK, Java Tech Edition for WebSphere v5



APAR status
Closed as program error.

Error description
The java process restarts.  In the stdout file of the process,
tracefile for the AdminServer java process, and the defined
stdout for AppServers, the following is logged
*** panic: double allocation failure
SIGABRT 6 (*) abort process
 stackpointer=330c51d8
.
The problem was observed on WAS 4.0.4 but it is not limited to
that version.  This is a jdk problem, so any jdk prior to the
build date in which this is fixed could manifest this problem.
.
The java full version of the system that this was observed on
is J2RE 1.3.1 IBM AIX build ca131-20020722
.
This was observed on AIX 4.3.3 ML10.  But this problem can occur
on any IBM jdk prior to the 20020905 build.
.
The problem is identified by SOV defect, 53382.
.
The problem that occurs is that the jvm restarts due to a
SIGABRT.  The java stack trace will look as follows.
"Servlet.Engine.Transports:749" sys_thread_t:0x39C40E68
  ----- Native Stack -----
 at 0xD0182398 in fcntl
 at 0xD0013E90 in _p_raise
 at 0xD0186B70 in raise
 at 0xD017F5DC in abort
 at 0xD1424900 in xmPanic
 at 0xD14318BC in lockedHeapAlloc
 at 0xD1432D98 in realObjAlloc
 at 0xD1433508 in targetedAllocMiddlewareArray
 at 0xD14EF400 in _jit_newarray
.
The jcore output of the problem will be
*** ERROR ***  SIGABRT raised by software in libjvm.a
(ip)=D1424900  at  libjvm.a  .xmPanic + 02EC

*** ERROR ***  probable GC double allocation failure (Java2 defe
(ip)=D14318BC  at  libjvm.a  .lockedHeapAlloc + 02D4
(ip)=D1432D98  at  libjvm.a  .realObjAlloc + 0114
(ip)=D1433508  at  libjvm.a  .targetedAllocMiddlewareArray + 009
(ip)=D14EF400  at  libjitc.a  ._jit_newarray + 00A4
.
This is fixed beginning with the 20020905.
Local fix
None.  The only solution is to upgrade the jdk.
The double allocation failure is a result of very low available
memory being handled incorrectly. To get into this situation
there must either be a memory leak or insufficient heap size
(possibly due to heap fragmentation).
   Run with verbosegc to monitor heap usage, ensurethat the
minimum heap size,-Xms, is at least half the max heap size,-Xmx;
this helps to ensure that objects that persist the life-time of
the JVM are allocated into a localized area), and that heapdumps
are enabled in case the process does run out of memory.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 using IBM JDK prior to 20020905 build.       *
****************************************************************
* PROBLEM DESCRIPTION: SIGABRT in /usr/lib/libpthreads.a, the  *
*                      JDK is in a _jit_newarray call when     *
*                      this occurs.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The JVM restarts due to a SIGABRT.
The java stack trace will look as follows:

"Servlet.Engine.Transports:749" sys_thread_t:0x39C40E68
----- Native Stack -----
at 0xD0182398 in fcntl
at 0xD0013E90 in _p_raise
at 0xD0186B70 in raise
at 0xD017F5DC in abort
at 0xD1424900 in xmPanic
at 0xD14318BC in lockedHeapAlloc
at 0xD1432D98 in realObjAlloc
at 0xD1433508 in targetedAllocMiddlewareArray
at 0xD14EF400 in _jit_newarray

This problem can occur on any IBM jdk prior to the 20020905
build. The problem is identified by SOV defect, 53382.
Problem conclusion
This is fixed beginning with the 20020905. The only solution is
to upgrade the JDK.
Temporary fix Comments
APAR information
APAR number PQ74194
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-05-14
Closed date 2003-05-16
Last modified date 2003-05-16

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
JDK          

SRLS

Fix information

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ74194
IBM Group: Software Group
Modified date: May 16, 2003