PQ85404: ABEND0C4,ABEND0C1 IN DEPLOYMENT MANAGER SERVANT REGION IN METHODSENDING_REPLY, IN MODULE BBOTTMSJ AFTER NULLPTREXCEPTION. | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description ABEND0C4 or ABEND0C1 may occur in method 'sending_reply' in module bbottmsj.cpp. This ABEND is occuring during thread termination, after a previous 'checkJavaException' is being processed on the thread. . Traceback stack for this problem is: BBOT_TransactionManager_JTA::sending_reply(ORB_Request&) BBO_BOA::copyResponseToCTL_FromSR(ORB_Request*) RestartThreadRtn CleanUpList::call_cleanup_routines(btcb*) CallThisThreadCleanUpRoutines(btcb*) RasAtThreadExit boss_thread_destructor CEEPGTFN CEEUCALL CEEOXKTD CEEOPE pthread_exit RasProcessTerm(int,unsigned int) checkJavaException(JNIEnv_*,unsigned char,unsigned char) checkJavaException(JNIEnv_*) ORBEJSBridge::CORBAinvoke(void*) threadDispatch(BOSS_Object_Key*,Internal_CORBA_Request&,ORB_ SR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*,TCB* SR_ExecutionRoutine CEEPGTFN . In this particular instance, the 'previous error' which caused the 'checkJavaException' was a 'ava.lang.NullPointerException' thrown from: com.ibm.ws.security.auth.ContextManagerImpl.clearCallerContext (ContextManagerImpl.java:1674)Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4/ABENDSOC4 or * * ABEND0C1/ABENDSOC1 in module BBOTOTS * * of the deployment manager or * * application server servant region. * **************************************************************** * RECOMMENDATION: * **************************************************************** The servant region of the deployment manager or application server can take an ABEND0C4/ABENDS0C4 or ABEND0C1/ABENDS0C1 during WebSphere's thread cleanup routine. The thread cleanup routine is called when a WebSphere address space is terminating. The transaction service releases a block of storage which is still referenced off a thread level control block. If code later in the cleanup routine references this storage, which may have been reused by another module, it could cause a protection exception. In this case, the protection exception occured in the sending_reply method of module bbottmsj. The traceback was as follows: BBOT_TransactionManager_JTA::sending_reply(ORB_Request&) BBO_BOA::copyResponseToCTL_FromSR(ORB_Request*) RestartThreadRtn CleanUpList::call_cleanup_routines(btcb*) CallThisThreadCleanUpRoutines(btcb*) RasAtThreadExit boss_thread_destructor CEEPGTFN CEEUCALL CEEOXKTD CEEOPE pthread_exit RasProcessTerm(int,unsigned int) checkJavaException(JNIEnv_*,unsigned char,unsigned char) checkJavaException(JNIEnv_*) ORBEJSBridge::CORBAinvoke(void*) threadDispatch(BOSS_Object_Key*,Internal_CORBA_Request&,ORB_ SR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*,TCB* SR_ExecutionRoutine CEEPGTFNProblem conclusion Code has been added to the transaction service to clear the reference in the thread control block before the storage is released. APAR PQ85404 is associated with SERVICE LEVEL W502005 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ85404.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ85404
IBM Group: Software Group
Modified date: Apr 3, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.