PQ92032: IMPROVE DIAGNOSTICS FOR OTS TIMEOUT ABEND EC3 REASON 04130005 TO INDICATE THREAD OF TIMED OUT REQUEST WHERE POSSIBLE | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Occassionally when a request governed by the OTS timer is dispatched in a servant region has been dispatched long enough to reach the limit of the OTS timeout value, when the servant region is abended with EC3 reason 04130005, the EC3 completion code may be marked on the thread for SR_WorkThread::RemoveAndProcessWork rather than the SR_ExecutionThread on which the thread was dispatched. In these cases, the svc dump taken for the abend EC3 reason 04130005 shows the EC3 completion code for the TCB with the following callback stack: BBOOSBOA SR_WorkThread::RemoveAndProcessWork(ThreadCleanUp*) SR_WorkRoutine . This apar is to improve the diagnostics and serviceability for these cases, where possible, to associate the EC3 abend with the SR_Execution thread containing the dispatched request rather than the SR_WorkThread timer thread.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: ABENDEC3/ABENDSEC3 reason code 04130005 * * is issued on the incorrect servant * * thread after a transaction timeout. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere terminated the incorrect servant region thread after a transaction timeout. The thread which was abended was the thread which requested the timeout, and not the one running the transaction which actually timed out. The net effect, termination of the servant region, was still accomplished. For serviceability, it would be helpful to abend the thread which the transaction was running on. The thread which is timed out will have the following call stack, and is not running any transaction: BBOOSBOA SR_WorkThread::RemoveAndProcessWork(ThreadCleanUp*) SR_WorkRoutineProblem conclusion When possible, after a transaction timeout, WebSphere will abend the thread running the transaction which timed out instead of abending the thread which requested the timeout. APAR PQ92032 is associated with SERVICE LEVEL W502015 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: PQ92036 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ92032.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 #: PQ92032
IBM Group: Software Group
Modified date: Oct 5, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.