PK38909: ADMINCLIENT GENERATE EXCESSIVE NO. OF TIME_WAIT STATE SOCKETS WHEN USING THE SOAP CONNECTOR

APAR status

• Closed as fixed if next.

Error description

• There are an excessive number of sockets created between RAD
  and the WAS server (SOAP port).  These are opened every few
  seconds and discarded fairly quickly.  This leaves behind a
  large number of sockets in TIME_WAIT state.
  .
  Examine the output of 'netstat -an' and look at all the sockets
  in TIME_WAIT state.  Over 100 (sometimes close to 200) have been
  seen in a test system.
  .
  Apparently every com.ibm.websphere.management.AdminClient
  "getters" call will create 2 sockets in TIME_WAIT state.
  

Local fix

• Shorten the period of TIME WAIT.  How to set this depends on the
  operating system.
  
  Or use RMI connector.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Websphere Application Server users of        *
  *                 version 6 who use Rational Application       *
  *                 developer.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: There is an excessive number of sockets *
  *                      created between Rational Application    *
  *                      Developer and the Application Server    *
  *                      (SOAP port). These are opened every few *
  *                      seconds and discarded fairly quickly.   *
  *                      This leaves behind a large number of    *
  *                      sockets in TIME_WAIT state.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The JMX calls (with SOAP connection) to the Websphere
  Application Server have created the excessive "TIME_WAIT"
  state sockets. Every com.ibm.websphere.management.AdminClient
  "getters" call will create 2 sockets in TIME_WAIT state.
  
  This APAR is being closed FIN with concurrence from the
  submitting customer. This means that a fix to this APAR is
  expected to be delivered from IBM in a release which is being
  developed at the time that the APAR was closed. The latest
  release of the product to exit development at the time this
  APAR was closed was: WebSphere Application Server version 6.1.
  

Problem conclusion

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

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP