Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Client is experiencing very slow performance and/or a hang condition when accessing a WebSphere application through the WebSphere Application Server Plugin. Review of the WebSphere Application Server Plugin log file showed the following error messages: ERROR: ws_common: websphereGetStream: Failed to get a socket, OS err=3452 ERROR: ws_common: websphereGetStream: Out of file/socket handles during request. ERROR: ws_common: websphereExecute: Failed to create the stream ERROR: ws_common: websphereHandleRequest: Failed to execute the transaction to xxxx on host xxxx; will try another one RROR: ws_common: websphereGetStream: socket descriptor=32899 exceeds socket descriptor limit of 32768 When the WebSphere plugin experiences a heavy load, which is described as more than 200 simultaneous requests at a time, some of the requests are dropped and marked as a WebSphere Application Server failure. At the same time a bad file descriptor error 3450 is displayed in the WebSphere plugin logs. The "Failed to get a socket" is thrown as a result of the default maximum file and socket descriptor per job limit being reached. The default max per job for the i5/OS is 200. The "socket descriptor=xxx exceeds socket descriptor limit of 32768" message is thrown when the integer value returned from the call to the socket API is larger than 32768. It was found the plugin should increase the default max file and socket descriptors per job if the default limit of 200 is reached. Also, the overall limit of 32K was found to be too small since valid integer socket values were being returned that were higher than the 32768 limit.
Local fix
Load balance the HTTP requests between HTTP Servers to reduce the number of file and socket descriptors per job.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server 6.1 and 7.0 * **************************************************************** * PROBLEM DESCRIPTION: An error, "err=3452", is displayed in * * the WebSphere plugin logs when the * * plugin experiences a heavy load. * **************************************************************** * RECOMMENDATION: Apply the 6.1.0.39 or the 7.0.0.19 fixpack * **************************************************************** When the WebSphere plugin experiences a heavy load, which is described as more that 200 simultaneous requests, some requests are dropped and marked as a WebSphere Application Server failure. At the same time, the following error is logged in the WebSphere plugin's log: "Failed to get a socket, OS err=3452".
Problem conclusion
To fix this problem, the WebSphere plugin's socket creation code is checked for "osIsOutOfHandles" error and the Job's capacity to create new sockets is incremented by a 100 and the socket creation is reattempted again. The fix for this APAR is currently targeted for inclusion in 6.1.0.39 and 7.0.0.19 fix packs. 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
PM32939
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-02-16
Closed date
2011-04-01
Last modified date
2011-04-01
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
R61W PSY
UP
R700 PSY
UP
Document Information
Modified date:
27 October 2021