IBM Support

PI91872: FD LEAK HAPPENS WHEN BINDEXCEPTION OCCURS IN CONNECTIONMANAGER

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • FD (file descriptor) leak happens when BindException occurs in
    ConnectionManager, increasing the file descriptors or using NIO
    does not work
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of WebSphere Application Server       *
    *                  observing                                   *
    *                  socket bind failures and high file          *
    *                  descriptor                                  *
    *                  counts                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: The server may leak a file descriptor   *
    *                      during a socket bind() failure          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    While creating a socket connection, if the socket fails to bind
    to
    the local address, a java.net.BindException is thrown. When
    handling this exception, the TCP Channel might not correctly
    close
    out the socket object, resulting in a leak of the file
    descriptor
    associated to this socket. This applies only to sockets that
    have
    had no successful I/O operations. The TCP Channel will throw a
    First Failure Data Capture (FFDC) similar to the following:
    com.ibm.ws.tcp.channel.impl.ConnectionManager 100
    Exception = java.net.BindException
    Source = com.ibm.ws.tcp.channel.impl.ConnectionManager
    probeid = 100
    Stack Dump = java.net.BindException:
    at sun.nio.ch.Net.bind0(Native Method)
    at sun.nio.ch.Net.bind(Net.java:594)
    at sun.nio.ch.Net.bind(Net.java:574)
    at
    sun.nio.ch.SocketChannelImpl.bind(SocketChannelImpl.java:658)
    at sun.nio.ch.SocketAdaptor.bind(SocketAdaptor.java:160)
    at
    com.ibm.ws.tcp.channel.impl.ConnectionManager.create(ConnectionM
    ana
    ger.java:255)
    at
    com.ibm.ws.tcp.channel.impl.ConnectionManager.getConnection(Conn
    ect
    ionManager.java:128)
    at
    com.ibm.ws.tcp.channel.impl.TCPConnLink.connectCommon(TCPConnLin
    k.j
    ava:253)
    at
    com.ibm.ws.tcp.channel.impl.TCPConnLink.connectAsynch(TCPConnLin
    k.j
    ava:232)
    at
    com.ibm.ws.channel.framework.impl.OutboundVirtualConnectionImpl.
    con
    nectAsynch(OutboundVirtualConnectionImpl.java:71)
    at
    com.ibm.rmm.ptl.tchan.transmitter.PTransmitter.establishConnecti
    onN
    onBlocking(PTransmitter.java:542)
    at
    com.ibm.rmm.ptl.tchan.transmitter.CheckConnectionPending.run(Che
    ckC
    onnectionPending.java:112)
    

Problem conclusion

  • The TCP Channel was modified to correctly close the socket.
    
    The fix for this APAR is currently targeted for inclusion in
    Java 6.0.16.60, Java 6.1.8.60, Java 7.0.10.20, Java 7.1.4.20, an
    Java 8.0.5.10.  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

    PI91872

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-12-25

  • Closed date

    2018-01-09

  • Last modified date

    2018-01-09

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI91872

Modified date: 09 January 2018


Translate this page: