PK05413: IN CONTROL REGIONS, PENDING ORB REQUEST NEVER ANSWERED, LEADING TO VARIOUS TIME OUT RELATED ERRORS | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When a timeout error occurs, such as EC3 & REASON CODE 04130004, happens and one of the WebSphere address spaces appear to be hung - not processing any requests - look to a the dump of the address space. I could be node agent, daemon, CR, the things that act as control regions. Do a nthreads display and review all of the WebSphere threads. You will see all of those threads hung up with the following at the top of their traceback stacks: Entry E Addr E Offset Statement Load Mod Serv PendingORBRequestBucket::waitPendingORBRequest(unsigned long 2A189A90 -00075442 BBOCOMM Session::recv_response(unsigned long,unsigned long*) 2A18FAC0 +00001060 BBOCOMM ORB_Request::comm_cr_sclt_locate_response(ORB_Request::Outbo 2AC39250 +000000D2 BBOBOA ORB_Request::comm_outbound_locate() 2AC36080 +00001328 BBOBOA CORBA::Request::Request(CORBA::Object_ORBProxy*,char*,unsign 2A3A6340 +00000760 BBOORB ORBEJSBridge::create_request(JNIEnv_*,bboojorb*,char*,unsign 2A354600 +00000964 BBOORB Java_com_ibm_ws390_orb_ClientDelegate_jorbCreateRequest 2ABAF510 +000009AE BBOBOA ..... .... ... This means this address space would sit indefinitely, while all the threads wait for a response that is not coming. The indefinite wait should eventually trigger some sort of time out erro to bring the situation to your atention.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: recv_response needs to handle bad * * GIOP headers and other exceptions * **************************************************************** * RECOMMENDATION: * **************************************************************** In recv_response bad GIOP headers and other exceptions can cause improper session cleanup. This can lead to hang conditions for all communication on the session and in some cases for the whole server.Problem conclusion Sessions are now properly terminated and cleaned up in recv_response. APAR PK05413 is associated with SERVICE LEVEL W502030 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: swg1PK05413.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 #: PK05413
IBM Group: Software Group
Modified date: Jun 2, 2005
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.