ABENDEC3 RSN=04130001 in WebSphere Application Server
 Technote (FAQ)
 
Problem
While running WebSphere Application Server for five to ten minutes an ABENDEC3 occurs. The following message is seen at the time of the abend:

BPXP0091 THREAD 1E9F34000000000C, IN PROCESS 67109509, ENDED
ABNORMALLY WITH CONDITION CODE 4FEC3000, REASON CODE 04130001.

The Application Server then recycles itself two to five times,then Application Server handles application requests for another five to ten minutes.
 
 
Solution
The dump analysis showed that there was a thread that timed out because the OTS timeout value of 300 seconds was reached. This timeout caused the ABENDEC3 RSN=04130001. This thread was the user application code that had just issued a "query" or "connect" to the OEM code, to connect and get data passed back. The
"request" or "connect" was not responded to and a timeout occurred.

The application code should set a timer just prior to connect to OEM and this timer should pop prior the 300 second OTS timeout value. The timer pop would then raise some type of user exception, that would avoid the OTS timeout value from being reached.

The application code was modified to make this change and when the new application code with the socket timeout had been deployed this problem was resolved.
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > EJB Container
Operating system(s): z/OS
Software version: 4.0.1
Software edition:
Reference #: 1163874
IBM Group: Software Group
Modified date: Mar 22, 2004