IBM Support

PM60529: SOCKET LEAK ON THE SOAP PORT

Fixes are available

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
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
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.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
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
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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Product Version: WebSphere Application Server 7.0.0.13
    
    OS and Additional Information:
    OS: Linux, version 2.6.18-238.el5
    Java: Java version = 1.6.0, Java Compiler = j9jit24, Java VM
    name = IBM J9 VM
    
    Problem Description:
    
    Many connections with the status of "CLOSE_WAIT", which are
    connecting to the SOAP port, will never be closed until the
    server is restarted.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0 and V8.0                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Many connections are seen with the      *
    *                      status of "CLOSE_WAIT" and are not      *
    *                      closed until the server is restarted.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Connections to the SOAP port are not closed and remain in
    'CLOSE_WAIT' state.  There may be some FFDC files written
    for AdminClient  ConnectionNotAvailable.
    After enabling SOAP traces, traces indicated that an
    SSLHandshakeException had occurred.
    [3/1/12 13:23:01:366 CET] 0000009b WSX509TrustMa E
    CWPKI0022E: SSL HANDSHAKE FAILURE:  A signer with SubjectDN
    "CN=<blah>, OU=<blah>, OU=<blah>, O=IBM, C=US" was sent from
    target host:port "<ip addr>:<soap port>".  The signer may need
    to be added to local trust store
    "/opt/IBM/WebSphere/wp_profile/config/cells/<cellname>/trust.p12
    " located in SSL configuration alias "NodeDefaultSSLSettings"
    loaded from SSL configuration file "security.xml".  The
    extended error message from the SSL handshake exception is:
    "PKIX path building failed:
    java.security.cert.CertPathBuilderException:
    PKIXCertPathBuilderImpl could not build a valid CertPath.;
    internal cause is:
    java.security.cert.CertPathValidatorException: The
    certificate issued by CN=<blah>, OU=Root Certificate,
    OU=<blah>, OU=<blah>, O=IBM, C=US is not trusted; internal
    cause is:
    java.security.cert.CertPathValidatorException: Certificate
    chaining error".
    

Problem conclusion

  • The SOAP code was modified to close the socket connection if
    an exception occurs during the SSL Handshake.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.25 and 8.0.0.4.
    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

    PM60529

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-16

  • Closed date

    2012-04-25

  • Last modified date

    2012-04-25

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM60529

Modified date: 25 April 2012