PK03607: WEBSPHERE ASID ABENDS WITH C9C21C3E, CR HAS MESSAGE BBOO0073E JAVA.LANG.OUTOFMEMORYERROR, SR HAS WTRN0008W: OBJ DESERIALIZED

 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
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.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.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Windows
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 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
5.0.2.12: WebSphere Application Server 5.0.2 Cumulative Fix 12
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.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
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
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
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.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for HP-UX
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
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
WebSphere Application Server for z/OS, Control Region abends.
with Reason code C9C21C3E.  Looking in the CR output, you see:
the following trace entry:
Trace: 2005/03/29 20:09:37.951 01 t=8A6088 c=UNK key=S2
                                                 (0000000A)
  Description: Log Boss/390 Error
  from filename: ./bbolrt.cpp
  at line: 1723
BBOO0073E Shasta Runtime function logJavaException detected that
the following exception occurred in the Java JVM.
Exception Message = java.lang.OutOfMemoryError
JVM Stack Trace = java.lang.OutOfMemoryError
.
Trace: 2005/03/29 20:10:16.685 01 t=8BD088 c=UNK key=P8
                                                     (13007002)
  FunctionName: com.ibm.ws390.tx.partnerLog.XaRecoveryTable
  SourceId: com.ibm.ws390.tx.partnerLog.XaRecoveryTable
  Category: ERROR
ExtendedMessage: WTRN0008W: Object cannot be deserialized. The
exception stack trace follows: java.io.StreamCorruptedException:
Caught EOFException while reading the stream header
.at java.io.ObjectInputStream.readStreamHeader
    (ObjectInputStream.java(Compiled Code))
.at java.io.ObjectInputStream.<init>
    (ObjectInputStream.java(Compiled Code))
.at com.ibm.ws390.tx.partnerLog.XaRecoveryTable.findRecoveryId
    (XaRecoveryTable.java:187)
.at com.ibm.ws390.tx.ResourceManagerData.getGlobalRecoveryID
    (ResourceManagerData.java:107)
.at com.ibm.ws390.tx.TransactionImpl.enlistResource
    (TransactionImpl.java:1303)
.at com.ibm.ws390.tx.TransactionManagerImpl.enlist
    (TransactionManagerImpl.java:861)
.at com.ibm.ws390.tx.TransactionManagerSet.enlist
    (TransactionManagerSet.java:508)
.at com.ibm.ejs.j2c.XATransactionWrapper.enlist
    (XATransactionWrapper.java:737)
.at com.ibm.ejs.j2c.ConnectionEventListener.interactionPending
    (ConnectionEventListener.java:743)
.at com.ibm.ejs.jms.JMSManagedSession.interactionPending
    (JMSManagedSession.java:988)
.at com.ibm.ejs.jms.JMSManagedSession.enlist
    (JMSManagedSession.java(Compiled Code))
.at com.ibm.ejs.jms.JMSMessageProducerHandle.enlist
    (JMSMessageProducerHandle.java:716)
.at com.ibm.ejs.jms.JMSQueueSenderHandle.send
    (JMSQueueSenderHandle.java:175)
.at com.cust.app.code.task.TaskBean.addTaskToQueue(Unknown
.at com.cust app.code.task.EJSLocalStatelessTask_c0f1f37a.
     addTaskToQueue(Unknown Source)
.at com.cust.app.code.putMessage(Unknown Source)(
.at com.cust.app.code.doTask(Unknown Source)
.at com.cust.app.code.onMessage(Unknown Source)
.at com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.
    run(MDBWrapper.java:205)
.at java.security.AccessController.doPrivileged(Native Method)
.at com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage(
    MDBWrapper.java:194)
.
Looking in the SVC Dump that is generated, which captures the
CR asid, and has a dump title of:
 Dump Title: COMPON=WEBSPHERE,Z/OS,COMPID=5655I3500,
             ISSUER=BBORMCDP,ERRNO=C9C21C3E
Formatting out the TCB which issued the BBOO0073E message in the
job output, the stack trace of this TCB is:
Function
--------
BBORMCDX
RMCDP_Class::takeSVC_Dump(unsigned long)
RasProcessTerm(int,unsigned int)
checkJavaException(JNIEnv_*,unsigned char,unsigned char)
checkJavaException(JNIEnv_*)
BBOT_XaRecoveryTableManager::getCurrentSerializedTable
   (bbotxpdm*)
BBOT_TransactionManager_CR::work_request_dispatch(acrwObj&)
ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*)
ACR_ExecutionRoutine
(unknown)
.
 Note that this TCB may not be marked as an error tcb in the
summary format output of the svcdump.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server Java Message    *
*                 Service (JMS) users                          *
****************************************************************
* PROBLEM DESCRIPTION: Problem with transaction log filling    *
*                      up.                                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Problem with transaction log filling up. This is caused by
an incorrect comparison to identify the number of transaction
log entries to log.
Problem conclusion
Fixed comparison to correctly identify number of transaction
log entries to log.

The fix for this APAR is currently targeted for inclusion
in cumulative fix 5.02.12.
Please refer to the recommended updates page for delivery
information:

http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information
APAR number PK03607
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-04-04
Closed date 2005-08-23
Last modified date 2005-08-23

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

APAR is sysrouted TO one or more of the following:

Modules/Macros
J2C          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PK03607
IBM Group: Software Group
Modified date: Aug 23, 2005