PK65014: JMS APPLICATIONS ARE SLOW TO CLOSE CONNECTIONS

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• JMS applications appear to be stuck for several seconds and
  then seem to be released at once which causes a performance
  problem.  This is seen with large numbers of JMS connections
  active at the same time.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the default messaging provider     *
  *                  for WebSphere Application Server 6.0 and 6.1*
  ****************************************************************
  * PROBLEM DESCRIPTION: The closing of JMS objects, for         *
  *                      example connections, is                 *
  *                      performed at a lower priority than      *
  *                      other JMS operations.  This can cause   *
  *                      a significant delay in systems with     *
  *                      large numbers of active JMS             *
  *                      applications.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An application calling close on a JMS object can be
  delayed for several seconds while other JMS operations on
  other threads are performed.  This only affects JMS close
  calls made over a network connection.
  
  In most configurations this is not a problem.  Systems with
  large numbers of JMS applications quickly creating, using, and
  closing JMS connections can see a delay during the closing of
  connections.  Trace or javacores will confirm the delay is in
  the close of the messaging object. This includes close methods
  on MessageConsumer, MessageProducer, QueueSender,
  QueueReceiver, TopicPublisher, TopicSubscriber, Session,
  QueueSession, TopicSession, Connection, QueueConnection or
  TopicConnection JMS objects. It can also include close methods
  on messaging objects used by IBM products to communicate
  directly with the default messaging provider in the
  com.ibm.ws.sib.comms.client package.
  
  This apar will add an additional tuning parameter that can be
  set that will allow JMS close calls to be given the same
  priority as other JMS calls.
  
  The property can be set in the sib.properties file needs to
  include the following:
  com.ibm.ws.sib.jfapchannel.INCREASE_CLOSE_PRIORITY=true
  
  The default is 'false'.  Using 'false' will give the same
  behaviour as before the APAR is applied.
  

Problem conclusion

• The APAR allows users to optionally change the behavior of JMS
  close calls to perform better in environments with large
  numbers of concurrent connections.
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 6.0.2.29 and 6.1.0.19.  Please refer to the Recommended
  Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  Note: In WebSphere Application Server V7 the default for
  com.ibm.ws.sib.jfapchannel.INCREASE_CLOSE_PRIORITY has been
  changed to 'true'.
  

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

  PLAT MSG COM

• Fixed component ID

  620400101

Applicable component levels

• R100 PSY

     UP