PK08361: REQUESTS TO INVOKE EJBS IN ANOTHER SERVER ON THE SAME LPAR HANG WHEN THE OTHER SERVER HAS BEEN STOPPED. | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description If an EJB in one server invokes an EJB in another server and both servers are located on the same LPAR, then the request could hang indefinitely if the other server is stopped. The thread with the hung EJB request will look like this: BBOOSOUT ORB_Request::comm_outbound_request() CORBA::Request::invoke() ORBEJSBridge::invoke_request(JNIEnv_*,bboojorb*,char*,unsigned ORBEJSBridge::build_and_invoke_request(JNIEnv_*,bboojorb*,char*, Java_com_ibm_ws390_orb_ClientDelegate_jorbInvokeRequest com/ibm/ws390/orb/ClientDelegate.jorbInvokeRequest(I.BIZI).B com/ibm/ws390/orb/ClientDelegate.invoke(Lorg/omg/CORBA/Object;Lo org/omg/CORBA/portable/ObjectImpl._invoke(Lorg/omg/CORBA/portabl mmipSelectInvokeJavaMethod _invoke - These threads will eventually time out unless protocol_http_timeout_output_recovery is set to SESSION. Setting this property to SESSION causes the thread to be hung for the life of the server. - This problem only affects EJB requests between two servers that are located on the SAME LPAR.Local fix Workarounds: (1) Stop the application that invokes the EJB in the other server before stopping the other server (2) Stop the SERVER containing the application invoking the EJB before stopping the other server (3) Move the other server onto a different LPARProblem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: All work coming into a server * * times out because all of the servant * * region threads went outbound to another * * server that was stopped. * **************************************************************** * RECOMMENDATION: * **************************************************************** When protocol_http_timeout_output_recovery is set to SESSION and the second server is stopped while the servant of the first server is going outbound to the second server. The first server becomes unable to process any new incoming work because all of the servant region threads are waiting for responses from the second server. The responses will never show up. Traceback of servant region threads waiting for responses. BBOOSOUT ORB_Request::comm_outbound_request() CORBA::Request::invoke() ...Problem conclusion Added an address space level resource manager to drive cleanup of server side sessions. This will cause the waiting servant region threads to be posted. APAR PK08361 is associated with SERVICE LEVEL W502033 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: PK09720 PK10168 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PK08361.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 #: PK08361
IBM Group: Software Group
Modified date: Sep 2, 2005
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.