IBM Support

PM20594: JAX-RPC CLIENTS MAY SLOW DOWN DUE TO OUTBOUND ONE-WAY CONNECTIONS NOT BEING RESET CORRECTLY

Fixes are available

6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Outbound one-way connections are not reset correctly in a
    busy environment and such connections could fill up the
    connection pool. You may notice the client application slowing
    down.
    
    Informational messages from the trace could show below:
    
    [8/12/10 15:50:55:353 CEST] 00000117 OutboundConne 1   Exit:
    findGroupAndReturnConnection() - WSWS3595I: Current pool size:
    30. Connections-in-use size: 18. Configured pool size: 100
    
    [8/12/10 16:02:02:426 CEST] 0000020c OutboundConne 1   Enter:
    WSWS3595I: Current pool size: 18. Connections-in-use size: 18.
    Configured pool size: 100
    
    In this case, there was a 5 minutes window that there was no
    HTTP activity.  The current pool size was not reduced to 0.
    

Local fix

  • No work around noted, candicate to be fixed in next release.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V6.1 and   *
    *                  V7.0 users of JAX-RPC Web services          *
    *                  clients.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Outbound one-way connections are not    *
    *                      reset correctly in a busy environment.  *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack containing this APAR.    *
    ****************************************************************
    Outbound one-way connections are not reset correctly in a
    busy environment and such connections could fill up the
    connection pool. The user may notice the client application
    slowing down.
    
    For example, following message shows the connection pool status:
    
    [8/12/10 15:50:55:353 CEST] 00000117 OutboundConne 1   Exit:
    findGroupAndReturnConnection() - WSWS3595I: Current pool size:
    30. Connections-in-use size: 18. Configured pool size: 100
    
    After 5 minutes without any HTTP and network activity, the
    connections should be reset and the current pool size should
    be reduced to 0.  However, following messages showed there are
    18 connections are still being used.
    
    [8/12/10 16:02:02:426 CEST] 0000020c OutboundConne 1   Enter:
    WSWS3595I: Current pool size: 18. Connections-in-use size: 18.
    Configured pool size: 100
    

Problem conclusion

  • There is a synchronization problem in JAX-RPC connection
    management code that causes some one-way connections to not get
    reset correctly in a busy environment.  The Web services
    runtime code has been changed to fix this problem.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.35 and 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

    PM20594

  • 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-08-16

  • Closed date

    2010-09-15

  • Last modified date

    2010-09-15

  • 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

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM20594

Modified date: 15 September 2010