This file gives an overview of how to enable and use the System Management Facilities (SMF) to collect and record system and job-related information.
The following guidelines provide instructions for finding diagnostic data in an SVC dump that can help you determine what timeout condition occurred:
ip summ format asid(x' address ')where address is the address space ID of the servant.
Find the TCB that had the EC3 completion code. Ignore any EC3 completion code on the "main" thread which is the 4th TCB listed in the summary format (the 1st one after the 3 MVS TCBs). The WebSphere main thread is the one that is waiting in BBO_BOA::impl_is_ready. No application requests are ever dispatched on this thread, therefore there is nothing to timeout. During timeout processing the main thread for the server region is also abended with EC3 as a mechanism of bringing the address space down. Thus the reason why the EC3 completion code may appear on the main thread. This is never the cause of a timeout though, only a result of timeout processing.
ip systrace all time(gmt)
You may not see the EC3 abend in systrace either as systrace can cover a small amount of time.
Reason code | Explanation |
---|---|
04130002 | The controller issued an ABTERM for this servant region because a transaction timeout occurred. Code under dispatch could have been in a tight loop. |
04130003 | The controller issued an ABTERM for this servant region because it was hung trying to move a controller request into the servant region. The target request was timed out, but the servant was currently copying the request. The controller checked the servant for progress at regular intervals, before taking action by issuing an ABTERM. |
04130004 | The controller issued a ABTERM for this servant region because the WLM queue timeout occurred. Code under dispatch could have been in a tight loop. |
04130005 | The controller issued an ABTERM for this servant region because a transaction timeout occurred. The transaction has timed out, but no current request associated with the transaction was found. The servant associated with the transaction will be terminated. |
04130006 | A controller thread encountered a problem while processing a request. The request has been queued to WLM and associated with a servant region. The termination of the associated servant region is needed to complete cleanup for the request. |
04130007 | The controller issued a ABTERM for this servant region because the HTTP OUTPUT timeout occurred. Code under dispatch could have been in a tight loop. |
httpRequest,
httpsRequestor
DispatchbyURIor some other method.
protocol_http_output_timeout(HTTP) and
protocol_https_timeout_output(HTTPS) timeout values will not be a factor. In other words, when the request is a
DispatchbyURImethod, the request is received through the RMI/IIOP protocol, so the
protocol_http* variables have no affect.