Fixes are available
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.47: Java SDK 1.5 SR16 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 new function.
Error description
With this APAR user need to set jvm property to be able to set the soap connection timeout value. Default behavior when there is connection, the socket connection will timeout based on the operating system timeout. There is no way to provide connection timeout to soap apache code to detect socket connection failure much faster. Following stack can be seen in the javacore: WebContainer : 0" (TID:0x3695C900, sys_thread_t:0x357E06EC, state:R, native ID:0x00897001) prio=5 4XESTACKTRACE at java/net/PlainSocketImpl.socketConnect(Native Method) 4XESTACKTRACE at java/net/PlainSocketImpl.doConnect (PlainSocketImpl.java:413) 4XESTACKTRACE at java/net/PlainSocketImpl.connectToAddress (PlainSocketImpl.java:274) 4XESTACKTRACE at java/net/PlainSocketImpl.connect (PlainSocketImpl.java:261) 4XESTACKTRACE at java/net/SocksSocketImpl.connect (SocksSocketImpl.java:389(Compiled Code)) 4XESTACKTRACE at java/net/Socket.connect(Socket.java:556) 4XESTACKTRACE at java/net/Socket.connect(Socket.java:504) 4XESTACKTRACE at java/net/Socket.<init>(Socket.java:412) 4XESTACKTRACE at java/net/Socket.<init>(Socket.java:255) 4XESTACKTRACE at org/apache/soap/rpc/Call.WASinvoke(Call.java: 395(Compiled Code)) 4XESTACKTRACE at com/ibm/ws/management/connector/soap/SOAPConnectorClient$4.run (SOAPConnectorClient.java:319) 4XESTACKTRACE at com/ibm/ws/security/util/AccessController.doPrivileged(AccessCon troller. java:118(Compiled Code)) 4XESTACKTRACE at com/ibm/ws/management/connector/soap/SOAPConnectorClient.reconne ct (SOAPConnectorClient.java:312) 4XESTACKTRACE at com/ibm/ws/management/connector/soap/SOAPConnectorClient.<init> (SOAPConnectorClient.java:184) 4XESTACKTRACE at sun/reflect/NativeConstructorAccessorImpl.newInstance0(Native Method) 4XESTACKTRACE at sun/reflect/NativeConstructorAccessorImpl.newInstance(NativeCons tructorA ccessorImpl.java:67(Compiled Code)) 4XESTACKTRACE at sun/reflect/DelegatingConstructorAccessorImpl.newInstance(Delega tingCons tructorAccessorImpl.java:45(Compiled Code)) 4XESTACKTRACE at java/lang/reflect/Constructor.newInstance (Constructor.java:522(Compiled Code)) 4XESTACKTRACE at com/ibm/websphere/management/AdminClientFactory.createAdminClien tPrivile ged(AdminClientFactory.java:382)
Local fix
No Workaround.
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM WebSphere Application Server * * version 6.1 and later. * **************************************************************** * PROBLEM DESCRIPTION: There is no way to configure JMX SOAP * * connector socket connection timeout. * **************************************************************** * RECOMMENDATION: * **************************************************************** There is no way to configure JMX SOAP connector socket connection timeout.
Problem conclusion
The code was changed to specify JMX SOAP connector socket timeout value. To specify the time out value set the JVM custom property com.ibm.websphere.management.soapSocketConnectionTimeout to the timeout value in seconds. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.47, 7.0.0.29, 8.0.0.6 and 8.5.0.2. 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
PM76124
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-10-30
Closed date
2012-12-12
Last modified date
2012-12-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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
29 October 2021