PQ53621: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0.1 FOR Z/OS AND OS/390. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This APAR addresses defects in WebSphere Application Server V4.0 for z/OS and OS/390.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ53621 addresses various problems * * in WebSphere Application Server V4.0.1 * * for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ53621 addresses the following problems in WebSphere Application Server V4.0.1 for z/OS and OS/390: WebSphere Application Server V4.0.1 for z/OS and OS/390 Servlets running at the PTF level UQ58859 and calling EJBs are not using the caller's identity for authorization checking as they did with WebSphere Application Server V4.0 for z/OS and OS/390 . Instead, the identity of the J2EE server region is being used. This can result in permission exceptions being raised. The message BBOU0530E is issued by the server. This problem is caused by the default RunAs setting. The default RunAs setting was run as server. This caused the unwanted authorization check on the server's identity rather than the caller's. Control regions can get into a state where they are no longer listening for new connections from clients. After receiving a connection request, the async IO accept processing attempts to create a session and start an async IO receive. If the receive fails, possibly with an errno of 1121, a long is thrown which goes all the way back to the dispatch code in bbooboat.cpp which logs an unexpected exception. There is no catch for this throw to reset the listener session to wait for new connection requests. The following problems can results when running WebSphere Application Server V4.0.1 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 APAR PQ53621 provides the following problem resolution: The default setting for RunAs has been changed to run as caller. Try/catch logic has been added to modules bbocsmri.cpp and bbocsmrs.cpp to reset the listener session to wait for new connection requests. 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 PQ53621 is associated with SERVICE LEVEL W401004 of WebSphere Application Server V4.0.1 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ59093 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ53621
IBM Group: Software Group
Modified date: Nov 2, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.