PQ57338: SHOULD NOT ABEND WITH EC3 WHEN HITTING TIME OUT SITUATION | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer was hitting a time out situation that caused the server region to ABENDEC3 with reason 04060026. What the abend code means is that work was queued from a CTL to SR and the SR did not pick up the work in the time frame specified by the OTS timeout environment variables. The SR then came along and tried to pick it up, but the work was no longer in the control region because he told the client it timed out. We decided that abending the SR, in this particular situation, is not the appropriate response, and the SR should stay active.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: ABENDEC3/ABENDSEC3 REASON=04060026 in a * * server region. * **************************************************************** * RECOMMENDATION: * **************************************************************** A timeout of an OTS transaction lead to an ABENDEC3, RSN=04060026 in an associated server region. The abend code indicates that work was queued from a control region to a server region and the server region did not pick up the work in the time frame specified by the OTS timeout environment variables. The server region then came along and tried to pick it up, but the work was no longer in the control region because it was cleaned up after responding to the client. The ABENDSEC3 RSN=04060026 was issued to terminate the server region.Problem conclusion To terminate the server region when the target request has already been responded to, is too drastic. Code has been changed in the server region to continue on to select another request to process. The following publication was revised as a result of APAR PQ57338: ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 Messages and Diagnosis GA22-7837-02 ________________________________________________________________ This APAR requires changes to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: http://www.ibm.com/software/webservers/appserv/ ________________________________________________________________ Chapter 14, pg. 558 (deleted message) EC3 04060026 Explanation: IBM Internal Only User Response: Contact the IBM Support Center ________________________________________________________________ APAR PQ57338 is associated with SERVICE LEVEL W401025 of WebSphere Application Server V4.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 #: PQ57338
IBM Group: Software Group
Modified date: Apr 2, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.