Fixes are available
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
When the control_region_timeout_delay property is being used (ie not set to 0), all requests with affinity for a Servant that is scheduled to ABEND are returned to the client with an error. However, when session persistence is enabled, many of these requests could have been requeued to another Servant and processed successfully. WebSphere should provide an option to requeue work in this scenario instead of returning everything to the client with an error.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: HTTP Request that could have been * * requeued to another servant was failed * * immediately * **************************************************************** * RECOMMENDATION: * **************************************************************** If a HTTP request times out when the request is under dispatch in a servant, the controller may mark the servant for termination. If the control_region_timeout_delay environment variable is set, all current HTTP requests with affinity to the same servant and in the WLM queue are failed immediately. Also, any subsequent HTTP requests with affinity to the same servant will be failed. The HTTP requests with affinity to the servant marked for eventual termination, could be requeued to run in another servant once the problem servant terminates.
Problem conclusion
Code has been added to allow HTTP requests with affinity to a servant that is to be terminated soon to be queued to WLM to await requeuing to another servant once the problem servant terminates. APAR PM82634 is currently targeted for inclusion in Fix Pack 8.0.0.7 of WebSphere Application Server V8.0 and Fix Pack 8.5.5 of WebSphere Application Server V8.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PM82634
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-02-12
Closed date
2013-04-26
Last modified date
2013-05-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 October 2021