PM52869: JMS APPLICATIONS WHICH USE CONNECTION POOLING TO A REMOTE SIB MESSAGING ENGINE CAN LEAK NETWORK CONNECTIONS OVER TIME

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When a JMS application in one server connects to a Service
    Integration Bus messaging engine located in a different server,
    WebSphere Application Server establishes a pool to manage the
    connections to the remote messaging engine.  If connections from
    this pool are rapidly created and destroyed, the application
    server can leak TCP/IP network connections.  The command
    'netstat -an' will show a growing number of connections in an
    ESTABLISHED state to the SIB port on the remote server.
    

Local fix

  • This leak occurs only when the application is on a different
    server than the SIB messaging engine.  No leak occurs when the
    application is on the same server as the messaging engine.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server V7.0 and   *
    *                  V8.0                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When applications using SIB connect to  *
    *                      Messaging Engines from an external      *
    *                      server using J2C connection pool there  *
    *                      is a leak observed on the physical      *
    *                      connections.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When Applications using SIB connect to Messaging Engine from an
    external server using J2C connection pool there is a leak
    observed on the physical connections. A netstat output would
    show that there is a constant increase in the number of
    physical connections being opened and the ones already opened
    are never being closed. From the heap dumps it can be seen that
    all the physical socket connections are being held due to the
    presence of a single conversation on them. The root cause for
    the problem was that the first connection on the socket which
    is being cloned during the create connection never is given to
    the J2C instead only cloned connections are given. Hence the
    parent connection never gets closed and stays there holding
    the socket from being released. This problem is especially
    observed if there are many connections that get opened from
    different consumers with different subjects every time.
    

Problem conclusion

  • The parent connection is also returned to the j2c pool for it
    to be utilised and close and ddestroyed by J2C, facilitating
    the release of the socket as well.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.25 and 8.0.0.5.  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

    PM52869

  • Reported component name

    WAS SIB & SIBWS

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-11-23

  • Closed date

    2012-04-10

  • Last modified date

    2012-04-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PM59340

Fix information

  • Fixed component name

    WAS SIB & SIBWS

  • Fixed component ID

    620800101

Applicable component levels

  • R300 PSY

       UP

  • R800 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
Service Integration Technology

Software version:

7.0

Reference #:

PM52869

Modified date:

2012-04-10

Translate my page

Machine Translation

Content navigation