PK43554: WEBSPHERE MQ HEADER DATA CORRUPTION UNDER LOAD USING WEBSPHERE APPLICATION SERVER 6

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

• The WebSphere MQ header buffer handling is not sufficiently
  thread-safe; under load the buffer position can be moved by a
  different thread such that the data is written to the wrong
  fields. Symptoms can include FFDC for an  IOException or
  InvalidHeaderValueException. A WebSphere MQ Client may receive
  a 2195 reason code.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of WebSphere Application Server        *
  *                 default messaging with an MQ Client Link.    *
  ****************************************************************
  * PROBLEM DESCRIPTION: An IOException or                       *
  *                      InvalidHeaderValueException may be      *
  *                      thrown when the MQ Client Link is under *
  *                      heavy load.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  It was possible for a thread to alter the position in memory
  of the MQ header fields which were in use by another thread.
  This resulted in an IOException or InvalidHeaderValueException
  being thrown by the MQ Client Link.
  

Problem conclusion

• The fix alters the way that the memory buffer is located and
  so ensures that each thread can correctly address it.
  

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