PQ76869: APPLICATION SERVER NOT RESPONDING TO STOP REQUEST AFTER A TRANSACTION HAS TIMED OUT WITH BBOU0713W | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description After a transaction has timed out in an application server as shown by message: BBOU0713W The transaction with URID '...<a hex urid string>...' has timed out after processing for more than xxx seconds. The transaction will be rolled back. The transaction XID is '...' when the application server is attempted to be stopped, either with a Stop command or as being recycled by the SM EUI, the server hangs and does not stop. The application control region has received the stop command and all "worker threads" show they are waiting for work. The problem is the transaction that was timed out in the server region did not have the opportunity to issue disassociate before the server region was ended from the timeout. It is the transaction the control region is waiting for before completing the stop of the server. This apar will have the control region handle this scenario. . If you are unsure you have a match for this problem, once a timeout has occurred where message BBOU0713W is observed, and once the stop request is issued and the application server hangs, issue the following MVS console commands (substituting your application server instance name for "BBOASR2A"): MODIFY BBOASR2A,TRACETOSYSPRINT=YES MODIFY BBOASR2A,DIAGDATA=ALL MODIFY BBOASR2A,TRACEINIT After issuing the DIAGDATA one, you may see message: BBOU0180E INCORRECT MODIFY COMMAND That is ok. Even though this message comes out, you should still see trace entries written to the sysprint of the application control region job. Then provide the WebSphere support team with the job output containing the output from the DIAGDATA modify command as well as a console dump of the hung application control region and all its server regions that are active. The WebSphere support team will use this information to confirm the problem.Local fix The application server must be manually cancelled.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: Server stop may hang after transaction * * timeout. * **************************************************************** * RECOMMENDATION: * **************************************************************** The transaction service and ORB maintain separate data structures to track transaction contexts. During a server stop, the ORB will wait for all transactions to complete before stopping the server. During this processing, only the ORB's data is checked. If a transaction timeout has ocurred, the ORB's data will contain information about the failed transaction and will hang waiting for their completion.Problem conclusion During server stop processing, the ORB will now use the transaction service tables to determine if all transactions have completed. The transaction service's tables only contain information about active transactions. By checking with the transaction service, the hang during stop is avoided. APAR PQ76869 is associated with SERVICE LEVEL W401601 of WebSphere Application Server version 4.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: 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 #: PQ76869
IBM Group: Software Group
Modified date: Oct 3, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.