PQ72125: APPSERVER HANGS/CRASHES AND USERS GET INTERNAL SERVER ERROR MESSAGES


APAR

APAR status
Closed as program error.

Error description
AppServer hangs/crashes and users get internal
server error messages
Action Taken:  If they look at the adminConsole it appears to be
running, but in reality, the AppServer is not running.
They have to force stop the AppServer and restart it to make
it work again.
The JVM heap size is set to 512min. 1024max.
The error appears to be coming from the native X windows
library in AIX: libXt.a.
.
Customer sees javacore files that are 0 bytes long.
The formatted core file shows that the failure is a SIGSEGV
in the libXt.a library.
fault_iar D0978660 inside module code area D09741C0-D09D9DA7 of
libXt.a (ip)=D0978660  at libXt.a  ._XtSortPerDisplayList + 00A8
fault_lr D0978644 inside module code area D09741C0-D09D9DA7 of
libXt.a (ip)=D0978644 at  libXt.a  ._XtSortPerDisplayList + 008C
fault_ctr D16A6034 inside module code area D167A000-D17E4D52 of
libawt.a(ip)=D16A6034  at  libawt.a  .xtError + 0000
fault_sp 30936A5C inside user data area 3019E000-42EF9000
fault_sp 30936A5C inside thread stack range 308F7000-30937408
D0978660: 901D0160  stw  base(29)=00000000, offs(0)=00000160,
addr=00000160
*** ERROR ***  definite memory access error (00000160) by r29
(00000000)
(ip)=D0978660  at  libXt.a  ._XtSortPerDisplayList + 00A8
    unwinding (old_sp=30936AAC old_ip=D0978660)
(ip)=D0978560  at  libXt.a  ._XtGetPerDisplay + 0064
    unwinding (old_sp=30936AFC old_ip=D0978560)
(ip)=D0979038  at  libXt.a  .XtWidgetToApplicationContext + 0064
    unwinding (old_sp=30936B3C old_ip=D0979038)
(ip)=D0986FE8  at  libXt.a  .XtTranslateCoords + 0028
    unwinding (old_sp=30936B9C old_ip=D0986FE8)
(ip)=D16B7D40  at  libawt.a  .awt_canvas_handleEvent + 0690
    unwinding (old_sp=30936C2C old_ip=D16B7D40)
(ip)=D16A5C04  at  libawt.a  .shouldDispatchToWidget + 0334
    unwinding (old_sp=30936C8C old_ip=D16A5C04)
(ip)=D16A68A8  at  libawt.a  .processOneEvent + 01B0
    unwinding (old_sp=30936D4C old_ip=D16A68A8)
(ip)=D16A5834  at  libawt.a  .awt_MToolkit_loop + 00C0
    unwinding (old_sp=30936DAC old_ip=D16A5834)
(ip)=D16A6E1C  at  libawt.a  .Java_sun_awt_motif_MToolkit_run +
00E8 unwinding (old_sp=30936E0C old_ip=D16A6E1C)
(ip)=D1370904  at  libjvm.a  .mmisInvoke_V_VHelper + 0108
    unwinding (old_sp=30936E6C old_ip=D1370904)
The customer is using WAS 3.5.4 which comes with JDK
ca122-20010313 (PTF 11).
.
KeyWords: jdk crash libXt SIGSEGV ca122-20010313
Local fix
There is no workaround for this problem.  A new jdk must be
applied.

This is jdk DEFECT:sov,58965
.

The fix has been integrated into 122 codebase. It is available
beginning with 122-20030315 builds for Windows, AIX, and Linux.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 release 3.5.4 running on AIX 4.3.3 ml-10     *
****************************************************************
* PROBLEM DESCRIPTION: AppServer hangs/crashes and users get   *
*                      internal server error messages.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The formatted core file shows that the failure is a SIGSEGV
in the libXt.a library.
fault_iar D0978660 inside module code area D09741C0-D09D9DA7 of
libXt.a (ip)=D0978660  at libXt.a  ._XtSortPerDisplayList + 00A8
fault_lr D0978644 inside module code area D09741C0-D09D9DA7 of
libXt.a (ip)=D0978644 at  libXt.a  ._XtSortPerDisplayList + 008C
fault_ctr D16A6034 inside module code area D167A000-D17E4D52 of
libawt.a(ip)=D16A6034  at  libawt.a  .xtError + 0000
fault_sp 30936A5C inside user data area 3019E000-42EF9000
fault_sp 30936A5C inside thread stack range 308F7000-30937408
D0978660: 901D0160  stw  base(29)=00000000, offs(0)=00000160,
addr=00000160
Problem conclusion
This is not a WebSphere defect, but a JDK defect. There is no
workaround for this problem.  A new jdk must be applied.
The reference jdk DEFECT is:sov,58965  It is available beginning
Temporary fix
Comments
APAR information
APAR numberPQ72125
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2003-03-17
Closed date2003-04-02
Last modified date2003-04-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
JDK
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ72125
IBM Group: Software Group
Modified date: 2003-04-02