PI91872: FD LEAK HAPPENS WHEN BINDEXCEPTION OCCURS IN CONNECTIONMANAGER

7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server

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 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

• R800 PSY

     UP

• R850 PSY

     UP

• R900 PSY

     UP