Fixes are available
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6
APAR status
Closed as program error.
Error description
When a cluster member is added to a collective, if the applications in the cluster member are receiving a large number of requests, there is a possibility that the plugin will produce a segfault when one of the first few requests to the new cluster member completes. A core file may be produced if the web server is configured for it.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the Dynamic Routing feature of IBM * * WebSphere Application Server Liberty * **************************************************************** * PROBLEM DESCRIPTION: With Liberty Dynamic Routing, adding a * * cluster member to a collective might * * cause the web server plug-in to * * segfault. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a cluster member is added to a collective, if the applications in the cluster member are receiving a large number of requests, there is a possibility that the plugin will produce a segfault when one of the first few requests to the new cluster member completes. A core file may be produced if the web server is configured for it.
Problem conclusion
When a cluster member is started for the very first time, there could be a short period of time between when the server is started, and when the server becomes a member of the cluster. Requests that are sent to the new cluster member that arrive when the server is not a member of the cluster and complete when the server is a member of the cluster will cause a segfault in the Web Server plugin. We have added code to handle the case where a request arrives when a server is not in a cluster and completes when the server is in a cluster. The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.4. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI81309
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-05-09
Closed date
2017-05-18
Last modified date
2018-08-20
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R900 PSY
UP
Document Information
Modified date:
02 November 2021