Fixes are available
PM22533; 6.1.0.35: there is no way to specify a timeout in sslutils.buildsslsock
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
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
When the System Management JMXClient invokes SOAPConnector with security enabled, the Apache soap code creates a SSL socket, and then invokes startHandshake() method. The issue here is that SOAP client code doesn't set a socket timeout until after the startHandshake() method completes. If there is a server which only accepts the SSL socket connection, but doesn't respond to SSL handshaking, the client code waits forever (the startHandshake() method never comes back unless the server closes the socket). This result in a hang.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All administrators of IBM WebSphere * * Application Servers. * **************************************************************** * PROBLEM DESCRIPTION: System management commands may hang * * in startHandshake() when security is * * enabled. * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this APAR. * * * **************************************************************** If security is enabled, system management commands may hang when communticating between nodes. The hang occurs within the SSLUtils.startHandshake() method. Sample stack: "WebContainer : 4457" (TID:0x00000001279EF600, sys_thread_t:0x00000001279E8470, state:R, native ID:0x00000000006B70DB) prio=5 at java/net/SocketInputStream.socketRead0(Native Method) at java/net/SocketInputStream.read(SocketInputStream.java:155(Compi led Code)) at com/ibm/jsse2/a.a(a.java:19(Compiled Code)) at com/ibm/jsse2/a.a(a.java:103(Compiled Code)) at com/ibm/jsse2/jc.a(jc.java:42(Compiled Code)) at com/ibm/jsse2/jc.g(jc.java:17(Compiled Code)) at com/ibm/jsse2/jc.a(jc.java:165(Compiled Code)) at com/ibm/jsse2/jc.startHandshake(jc.java:35(Compiled Code)) at org/apache/soap/util/net/SSLUtils.buildSSLSocket(SSLUtils.java:2 85(Compiled Code))
Problem conclusion
A new socket timeout property is used to control the socket time-out while creating an SSL connection used by system management. This time-out value is now set on the socket prior to starting handshake negotiation. The new JVM property is: org.apache.soap.util.net.SSLUtils.buildSSLSocket.timeout It is specified in milliseconds. The default value is 600000 (10 minutes or 600 seconds) Note, this change only creates a time-out, it does not address the core problem where the server accepts the connection but never responds. The thread will still appear hung until the time-out occurs. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.15. 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
PM22533
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-09-14
Closed date
2010-10-29
Last modified date
2012-04-12
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
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
Document Information
Modified date:
24 October 2021