Fixes are available
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
When using the Intelligent Mangement enabled plug-in for the IBM HTTP Server there can been numerous GSK_WOULD_BLOCK messages logged in the http_plugin.log when the web servers start, especially if there is a number of web servers sharing the same plugin-cfg.xml. This is because the initial connector,the XD_AGENT, that is selected for use is always the first connector in the order listed in the plugin-cfg.xml.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Intelligent Management enabled * * plug-in for IBM HTTP Server * **************************************************************** * PROBLEM DESCRIPTION: An unusually high number of * * GSK_WOULD_BLOCK messages on web * * server start with Intelligent * * Management Enabled Plugin. * **************************************************************** * RECOMMENDATION: * **************************************************************** When using the Intelligent Mangement enabled plug-in for the IBM HTTP Server there can been numerous GSK_WOULD_BLOCK messages logged in the http_plugin.log when the web servers start, especially if there is a number of web servers sharing the same plugin-cfg.xml. This is because the initial connector,the XD_AGENT, that is selected for use is always the first connector listed in the plugin-cfg.xml. When too many web servers attempt to connect to the same connector (XD_AGENT) it is possible to consume all of the available threads for that connecto which can cause connection failures in the form of the GSK_WOULD_BLOCK errors. The next connector in the list is then used to establish a new connection. The problem will normally correct itself but this fix will randomly select a connector for the initial selection to better distribute the workload and avoid these errors.
Problem conclusion
To lessen the initial traffic to that one connector, the code is being changed to select the initial connector at random from the list rather than always choosing the first one. This will increase the chances that the startup of web servers will choose different connectors and avoid using all of the available threads on the first connector which necessitates a failover to other connectors in the list. It will not eliminate the existence of the message, but it should cause it to appear less frequently. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.8. 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
PI49194
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-09-23
Closed date
2015-10-23
Last modified date
2015-10-23
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
R850 PSY
UP
Document Information
Modified date:
28 April 2022