IBM Support

PM39926: WEBSPHERE APPLICATION SERVER HOSTING A MESSAGING ENGINE RUNS OUT OF FILE DESCRIPTORS

Fixes are available

7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
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.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
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.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

  • A Websphere Application Server (WSAS) server hosting a
    messaging engine can run out of file descriptors.  The
    following Exception will be seen in the SystemOut.log:
    
    java.net.SocketException: Too many open files
    
    This exception can affect any WSAS server component using
    TCP/IP and is not restricted to the Servivce Integration Bus,
    although a messaging engine will be running in the server
    affected.
    
    Platform specific tools such as 'lsof' and 'netstat' can be
    used to determine that there are many open inbound TCP/IP
    connections to either the SIB_ENDPOINT_ADDRESS or
    SIB_ENDPOINT_SECURE_ADDRESS port.
    
    These symptoms may also be associated with high heap usage.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server        *
    ****************************************************************
    * PROBLEM DESCRIPTION: TCP/IP connection leak for              *
    *                      connections to either                   *
    *                      SIB_ENDPOINT_ADDRESS or                 *
    *                      SIB_ENDPOINT_SECURE_ADDRESS port.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In WebSphere Application server an optimization has been
    implemented to avoid unnecessary closing and opening of Core
    SPI Connections.  When such a Connection is closed, it
    is cached for use later by another thread.
    With the Service Integration Bus JMS Resource Adapter, when a
    JMS ManagedConnection is destroyed a Core SPI Connection is
    closed and cached.  However, the way the JMS Resource Adapter
    recreates Core SPI Connections prevents the cached Core SPI
    Connections being reused.  Consequently the Core SPI
    Connection cache grows indefiniately.
    

Problem conclusion

  • This APAR resolves the problem by ensuring the Core SPI is not
    cached when it is closed by the JMS Resource Adapter.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.21 and 8.0.0.3.  Please refer to the Recommended
    Updates page for delivery information:
    
    http://www.ibm.com/support/docview.wss?rs=180&uid=sw
    g27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM39926

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-24

  • Closed date

    2011-07-30

  • Last modified date

    2011-07-30

  • 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

    PLAT MSG COM

  • Fixed component ID

    620800101

Applicable component levels

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PM39926

Modified date: 30 July 2011