IBM Support

PI14101: UNDER HEAVY LOAD JAX-WS WEB SERVICE OUTBOUND POOL MAY LEAK CONNECTIONS.

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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Under heavy load JAX-WS WebService outbound pool may run out of
    connections, leaving connections in use forever. The following
    exception indicates the symptom of the issue when connections
    are not closed.
    
    [3/12/14 6:05:48:027 MST] 0005334e AbstractAsync 3   Sync
    operation timed out
    [3/12/14 6:05:48:041 MST] 0005334e HttpServiceCo 3
    IOException, closing the reads: java.net.SocketTimeoutException:
    Async
    operation timed out
    [3/12/14 6:05:48:045 MST] 0005334e HttpServiceCo 3   Preparing
    connection for closure
    [3/12/14 6:05:48:045 MST] 0005334e HttpServiceCo 3   Throwing
    exception back to caller.
    [3/12/14 6:05:48:685 MST] 0005334e HttpOutRespon 3   Failed to
    get next body buffer
    [3/12/14 6:05:48:706 MST] 0005334e StAXOMBuilder W
    org.apache.axiom.om.impl.builder.StAXOMBuilder parserNext
    Attempt to access a parser that has thrown a parse exception
    before; rethrowing the original exception.
    

Local fix

  • restart application server process.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  JAX-WS web services.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When time out exception happens, the    *
    *                      current in use connection could not     *
    *                      be reset and released.                  *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack containing this APAR.    *
    ****************************************************************
    When reading the response body buffer, if a time out exception
    happens, the current in use connection could not be reset and
    released. It will always stay in "in used" state and can not
    be reused. That will cause the connection resources in the
    connection pool to run out of connections.
    

Problem conclusion

  • Fixed the problem by adding the reset method to reset and
    release the connection for reuse if a time out exception
    happens.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.33, 8.0.0.9 and 8.5.5.3.  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

    PI14101

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-19

  • Closed date

    2014-05-02

  • Last modified date

    2014-05-21

  • 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 APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 8.0

Reference #: PI14101

Modified date: 21 May 2014