PQ97166: INFINITE LOOP IN COM.IBM.EJS.RAS.RASHELPER WHEN A NULLPOINTEREXCEPTION IS CAUGHT AFTER A PARKHANDLE CALL

 Fixes are available

5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for AIX
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for HP-UX
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Linux
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for HP-UX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Solaris
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Windows
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Solaris
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Windows
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for AIX platforms
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Solaris
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Linux
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Solaris
6.0.0.2: WebSphere Application Server Version 6.0.0 Fix Pack 2
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Windows
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for AIX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for AIX
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Linux
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for HP-UX platforms
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for OS/400 platforms
5.0.2.12: WebSphere Application Server 5.0.2 Cumulative Fix 12
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for HP-UX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for AIX
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for AIX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Solaris platforms
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Linux
6.0.0.3: WebSphere Application Server V6.0.0 Fix Pack 3
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Solaris
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Windows
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Solaris
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Linux
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for HP-UX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for AIX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Windows
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Solaris
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Windows
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for AIX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Linux
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for AIX
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Windows
5.0.2.13: WebSphere Application Server 5.0.2 Cumulative Fix 13
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for HP-UX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for AIX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Windows
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Windows platforms
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Linux platforms
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Linux
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for HP-UX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for HP-UX
6.0.1.2: WebSphere Application Server Version 6.0.1 Fix Pack 2
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for AIX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Linux
6.0.1: WebSphere Application Server Version 6.0 Refresh Pack 1
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Linux
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for HP-UX



APAR status
Closed as program error.

Error description
EXTERNAL SYMPTOMS:
This problem will manifest itself as a performance problem.
The AppServer stops serving many requests.
   It will likely also cause the AppServer jvm to crash with a
java.lang.StackOverflowError.
   The CPU utilization will likely be higher, since one of the
WAS threads is in a tight loop.  The loop is in the exception
processing of WebSphere.  A thread dump taken at the time the
loop is executing would show one thread like this one:
"Servlet.Engine.Transports : 1" daemon prio=5 tid=0x14db590
nid=0x8b runnable [0xceeeb000..0xcef019d8]
 at java.lang.Throwable.printStackTrace0(Native Method)
 at java.lang.Throwable.printStackTrace(Throwable.java:204)
 at
com.ibm.ejs.ras.RasHelper.printStackTrace(RasHelper.java:206)
 at
com.ibm.ejs.ras.RasHelper.printStackTrace(RasHelper.java:245)
 at
com.ibm.ejs.ras.RasHelper.printStackTrace(RasHelper.java:245)
 at
com.ibm.ejs.ras.RasHelper.printStackTrace(RasHelper.java:245)
 at
com.ibm.ejs.ras.RasHelper.printStackTrace(RasHelper.java:245)
(This last line will be repeated many, many times.)
 at
com.ibm.ejs.ras.RasHelper.throwableToString(RasHelper.java:191)
 at
com.ibm.ejs.ras.MessageEvent.convertParameters(MessageEvent.java
:438)
 at com.ibm.ejs.ras.MessageEvent.<init>(MessageEvent.java:196)
 at
com.ibm.ejs.ras.TraceEventGeneratorImpl.fireMessageEvent(Tr.java
:1389)
 at com.ibm.ejs.ras.Tr.error(Tr.java:568)
 at
com.ibm.ejs.j2c.ConnectionManager.parkHandle(ConnectionManager.j
ava:1246)
. This is all in one t


MESSAGES LOGGED:
[03/11/04 19:00:12:470 GMT]    ff6e0 MCWrapper     E J2CA0021E:
An exception occurred while trying to get a Connection from the
Managed Connection resource No longer available :
java.lang.NullPointerException
 at com.ibm.ws.rsadapter.spi.WSConnectionRequestInfoImpl.
hasSameUserAndPassword(WSConnectionRequestInfoImpl.java:257)
 at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.
replaceCRI(WSRdbManagedConnectionImpl.java:1363)
 at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.
associateConnection(WSRdbManagedConnectionImpl.java:2405)
 at com.ibm.ejs.j2c.MCWrapper.associateConnection(MCWrapper.
java:1618)
 at com.ibm.ejs.j2c.ConnectionManager.parkHandle
(ConnectionManager.java:1239)
 at com.ibm.ejs.j2c.HandleList.parkHandle(HandleList.java:378)
 at com.ibm.ejs.j2c.HandleCollaborator.postInvoke
(HandleCollaborator.java:117)

   The ffdc files for the AppServer will show that there is a
javax.resource.ResourceException that precedes the
NullPointerException that causes the recursive loop in
the RasHelper class.  This ResourceException is occurring on a
call from
com.ibm.ejs.j2c.HandleList.parkHandle.


RECREATION STEPS:
   A significant cause of this problem is a connection factory
defined in the resources.xml in that either it does not have the
parameter InactiveConnectionSupport in its parameters
or that parameter is set to false.

The trace will indicate if this is the case,
The trace shows the result of the missing property:
[04/11/04 12:22:02:054 GMT]
   1f7708 ConnectionFac d InactiveConnectionSupport not
specified for
J2C Connection Factory SMART_Driver_CF.  Default will be false

SEARCH KEYWORDS:
     Hang java.lang.StackOverflowError StackOverflowError
parkHandle Connection Manager associate RASHelper
printStackTrace infinite loop J2CA0021E
Local fix
One possible fix is to Set the InactiveConnectionSupport to
True.  This is in the resources.xml file.  The line with
       <resourceProperties xmi:id="J2EEResourceProperty_32"
name="InactiveConnectionSupport" type="java.lang.Boolean"
value="true"
            description="Specify whether connection handles
support implicit reactivation. (Smart Handle support). Value may
be &#34;true&#34; or &#34;false&#34;."/>
A value of "false" can cause this problem to occur.
This line in defined for a
  <resources.j2c:J2CResourceAdapter xmi:id="builtin_rra"
name="WebSphere Relational Resource Adapter"
description="Built-in Relational Resource Adapter for Container
Managed Persistence"
archivePath="${WAS_LIBS_DIR}/rsadapter.rar">

.
Another possible fix is to prevent the ResourceException that
led to this happening.  This can be done by closing all
connections explicitly.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server customers who   *
*                 use JCA functionality                        *
****************************************************************
* PROBLEM DESCRIPTION: A configuration error with respect to   *
*                      the "InactiveConnectionSupport"         *
*                      property could result in a JVM          *
*                      OutOfMemory crash.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A CMPConnectionFactory which referenced the Application Server
"builtin_rra" Resource Adapter for JDBC had inadvertently been
configured without the InactiveConnectionSupport property.  A
transaction ended without a connection being closed.  This put
the JCA code down an error path.  In the error path a
ResourceException was created and its LinkedException field
was set to reference itself, rather than the underlying
exception.  When the logging code tried to parse the
self-referencing exception, the recursion led to the
OutOfMemory crash of the JVM.
Problem conclusion
The self-referencing ResourceException was changed to reference
the underlying Exception.

The fix for this APAR is currently targeted for inclusion in
fixpack 5.0.2.10 and 5.1.1.3. Please refer to the Recommended
Updates page for delivery dates:

http://www-1.ibm.com/support/docview.wss?rs=180
&context=SSEQTP&uid=swg27004980
Temporary fix Comments
APAR information
APAR number PQ97166
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00S
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-11-12
Closed date 2004-12-08
Last modified date 2005-02-16

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
J2C          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00S
Software edition:
Reference #: PQ97166
IBM Group: Software Group
Modified date: Feb 16, 2005