IBM Support

PI12744: Connection timeout property of SOAP client ineffective in some cases

Fixes are available

7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The JVM property
    com.ibm.websphere.management.soapSocketConnectionTimeout
    does not work if a remote host drops offline after a
    connection was previously established.  The connection timeout
    will revert to the default of the underlying hardware platform.
    
    A thread dump will show a hung thread as follows:
    void
    java/net/PlainSocketImpl.socketConnect(java.net.InetAddress,
    int, int)  (Native Method)
    void
    java/net/PlainSocketImpl.doConnect(java.net.InetAddress, int,
    int)  source: PlainSocketImpl.java:370
    void
    .........
    
    org/apache/soap/util/net/SSLUtils.buildSSLSocket(String, int,
    String, int, String, String, String)  source: SSLUtils.java:259
    ........
    com/ibm/ws/management/connector/soap/SOAPConnectorClient$4.run()
    source: SOAPConnectorClient.java:373
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0, V8.0, and V8.5                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: The JVM property                        *
    *                      com.ibm.websphere.management.soapSocket *
    *                      ConnectionTimeout does not work in      *
    *                      some cases                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Connections to remote hosts were tested with a timeout
    on the initial attempt, but this result was then cached and
    reused without a timeout in subsequent attempts.  If a remote
    host dropped offline after the initial connection, a
    subsequent connection attempt to that host could change to the
    operating system default value, which might be too long.
    

Problem conclusion

  • The code is corrected to use the timeout from the JVM property
    consistently for both initial and subsequent connection
    attempts.
    
    APAR PI12744 is currently targeted for inclusion in Fix Packs
    7.0.0.33, 8.0.0.9, and 8.5.5.3 of WebSphere Application Server.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI12744

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-28

  • Closed date

    2014-03-20

  • Last modified date

    2014-07-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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UI18561

       UP14/06/21 P F406

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PI12744

Modified date: 01 July 2014