IV11947: UPGRADING TO WEBSPHERE MQ CLASSES FOR JMS 7.0.1.5 RESULTS IN BACKED OUT MESSAGES HAVING A DIFFERENT MESSAGE ID TO ORIGINAL

WebSphere MQ V7.0 Fix Pack 7.0.1.9
Fix Pack 7.1.0.2 for WebSphere MQ V7.1

APAR status

• Closed as program error.

Error description

• After upgrading the WebSphere Application Server to v7.0.0.19,
  when messages are moved to the backout queue (BOQNAME) after
  reaching their backout threshold count (BOTHRESH), the message
  IDs are different to their original value, prior to the
  backout.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the WebSphere MQ classes for JMS,
  who are making use of the poison message handling functionality
  provided by the WebSphere MQ classes for JMS, including:
  
  - The WebSphere MQ V7 classes for JMS.
  - The WebSphere MQ V7 Resource Adapter.
  - The WebSphere Application Server V7 WebSphere MQ messaging
  provider.
  - The WebSphere Application Server V8 WebSphere MQ messaging
  provider.
  - The WebSphere Application Server V6.1 WebSphere MQ messaging
  provider who have configured the WebSphere variable
  MQ_INSTALL_ROOT to point to a WebSphere MQ V7 installation.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows) +Java
  ****************************************************************
  PROBLEM SUMMARY:
  When a message reaches its backout threshold, and is processed
  by the poison message handling functionality of the WebSphere
  MQ classes for JMS, the message is moved to the backout requeue
  queue, as defined by the WebSphere MQ queue property 'BOQNAME'.
  
  A code change introduced into WebSphere MQ classes for JMS
  v7.0.1.5 resulted in the MQMD properties of the backed out
  message not being migrated over from the original message.
  
  For example, one of these properties which was not retained was
  the JMS message ID, resulting in the backed out message having
  a new generated message ID, which was different to that of the
  original message.
  

Problem conclusion

• The MQMD of the backed out message is now properly migrated
  across from the original message to the message put to the
  backout queue.
  
  | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0005       |
  | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0005       |
  | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0005   |
  | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0005      |
  | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0005     |
  | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0005     |
  | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0005       |
  | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0005 |
  | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0005     |
  | MDVREGR 7.0.1-WS-MQ-Windows-FP0005        |
  
  | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0006       |
  | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0006       |
  | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0006   |
  | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0006      |
  | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0006     |
  | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0006     |
  | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0006       |
  | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0006 |
  | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0006     |
  | MDVREGR 7.0.1-WS-MQ-Windows-FP0006        |
  
  | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0007       |
  | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0007       |
  | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0007   |
  | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0007      |
  | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0007     |
  | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0007     |
  | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0007       |
  | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0007 |
  | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0007     |
  | MDVREGR 7.0.1-WS-MQ-Windows-FP0007        |
  
  | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0008       |
  | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0008       |
  | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0008   |
  | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0008      |
  | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0008     |
  | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0008     |
  | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0008       |
  | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0008 |
  | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0008     |
  | MDVREGR 7.0.1-WS-MQ-Windows-FP0008        |
  
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.1       7.1.0.2
  v7.0       7.0.1.9
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

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:

  PM59590

Fix information

• Fixed component name

  WMQ AIX V7

• Fixed component ID

  5724H7221

Applicable component levels

• R701 PSY

     UP