PQ53149: ABEND0C4 IN SNOOZERS::MOVESTACKTOQ() OR LOOP IN SNOOZERS::PROCESSDEREGISTERQ() 01/10/15 PTF PECHANGE

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Abend0c4 pic10 in BBOEJB1, Snoozers::moveStackToQ() + 0xDE.
Stacktrace looks like,
Snoozers::moveStackToQ()
Snoozers::getExpiredEvent()
TimerDaemonThread::RemoveAndProcessWork()
TimerDaemonThreadRoutine
CEEPGTFN
main
Can also appear as a loop in Snoozers::processDeregisterQ().
.
Additional symptom:
ABENDU4088 in Systems Management Control Region, when running
BootStrap Phase 1,
Traceback has:
pt_malloc(unsigned int)
Snoozer::operator new(unsigned int)
Timers::deregisterSnoozeAlarm(SnoozeAlarm*)
BBOT_TransactionAlarm::disableAlarm()
BBOT_TransactionFactoryRep::scheduleTxForDeletion(BBOT_Trans
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 for z/OS and OS/390.                    *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ53149 addresses various problems *
*                      when running WebSphere Application      *
*                      Server V4.0 for z/OS and OS/390 with    *
*                      multiple clients.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Problem Summary:
----------------------------------------------------------------
The following problems can results when running WebSphere
Application Server V4.0 for z/OS and OS/390 with multiple
clients:

ABEND0C4 ABENDSOC4 can occur in method Snoozers::moveStackToQ()
module (bbootmq.cpp). WebSphere's internal timer services have
a serialization error. There is a serialization problem in a
re-use stack class, Stack_DT_CDS (bboustdt.h), that the internal
timer services exploit. The serialization problem in bboustdt.h
may lead to an element remaining in the stack after its been
"popped".  This can lead to double processing of the element.
Which will result in double releases, storage overlays, and/or
abends (ABEND0C1, ABENDS0C1, ABEND0C4, ABENDS0C4).

Storage overlays resulting in various ABEND0C4 ABENDS0C4 can
occur in Server control regions due to a double release of an
otid_t's storage was being done in method deleteTransaction
module bbottf.cpp.

Storage overlays resulting in various ABEND0C4 ABENDS0C4 can
occur in Server control regions due to a double release of an
IOR in destructor method  BBOT_TransactionCoordinatorRep in
module bbottcr.cpp.

There exists multi-client/thread classloader problem. The
problem is that multiple threads can get to the point of
defining the class to the JDK at the same time. The second
one that tries to do the define will fail with the
java.lang.LinkageError indicated in the following stack trace.

The following sample partial stack trace shows the exception
issued as a result of this class loader problem. To see this
trace you will need to at least have
com.ibm.ejs.util.jar.JarClassLoader=event=enabled active.
More often than not it will be a failure loading a
<class name>_Tie object class. If it fails and the client
code retries it will work.

Trace: 2001/10/16 19:04:21.845 01 t=8D0788 c=2.D key=P8
  FunctionName: com.ibm.ejs.util.jar.JarClassLoader
  SourceId: com.ibm.ejs.util.jar.JarClassLoader
  Category: EVENT
  ExtendedMessage: Exception java.lang.LinkageError: trying to
  refine class <class name>_Tie
  (bad class loader?) from defineClass call for class:
  <class name>_Tie;
  value 1 = java.lang.LinkageError: tryng to refine class
  <class name>_Tie (bad class loader?)
Problem conclusion
The seialization error in Stack_DT_CDS has been fixed.

Method deleteTransaction in module bbottf.cpp was modified to
correct the double release of otid_t storage.

Destructor method  BBOT_TransactionCoordinatorRep in
module bbottcr.cpp was modified to correct the double release
of IOR storage.

The class loader has been modified such that it allows for and
recovers from the situation where multiple threads can get to
the point of defining a class to the JDK at the same time.

APAR PQ53149 is associated with SERVICE LEVEL W400048 of
WebSphere Application Server V4.0 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ53149
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED PER
PE YesPE
HIPER NoHIPER
Submitted date 2001-10-08
Closed date 2001-10-22
Last modified date 2001-11-02

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOAPCEI BBOAPIAI BBOAPIOI BBOAPXLI BBOCOMM BBOCORBA
BBODDAUT BBOFRCGD BBOIBOIM BBOIDRMI BBOIGTID BBOIIMA
BBOIKEYS BBOIROOT BBOI3PLI BBOJJU BBOLRT BBOMDDLO
BBOMIBO BBOMSBO BBOMSCO BBOMUTIL BBOOBOAI BBOOBOAT
BBOOCRHT BBOOCSIT BBOOORB BBOOORBR BBOOORRG BBOOORSA
BBOOORSF BBOOSMF BBOOSMFT BBOOSRWT BBOOTMOT BBOOTMQ
BBOOTMQE BBOOTMTR BBOOTRD BBOPBO BBORAS BBOSEC
BBOSLHM BBOSNMO BBOSQ03 BBOSTXI BBOTBRT BBOTOTSJ
BBOTTCR BBOTTF BBOTTRC BBOUBINF BBOZ0812 BBOZ0813

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R400 PSY UQ59044    UP01/10/26 P F110

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ53149
IBM Group: Software Group
Modified date: Nov 2, 2001