IT18813: Queue manager can call xa_commit to an external XA resource manager even after failure to write its own log records

APAR status

• Closed as program error.

Error description

• The user unmounted the log file system underneath the queue
  manager.  The queue manager therefore failed to write its own
  log record for a commit operation.  But the queue manager
  continued to call xa_commit to an external XA Resource Manager
  (a database product).
  
  This led to the update being made in the external database
  product, but not within the queue manger's own resources (a
  queue).
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Applications using the two-phase commit functionality of a queue
  manager.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The log file system had been removed from underneath MQ.  It
  therefore lost ability to write any information about
  transactions or persistent messages to its transaction logs.
  
  When the queue manager failed to write its own log record, it
  should have ended immediately, and allowed the next run of the
  queue manager (when the log file system was made available
  again) to restore the integrity of the two-phase-commit
  transaction.
  

Problem conclusion

• The MQ code has been corrected so that, if the queue manager
  fails to write its own log record, it ends immediately, and
  allows the next run of the queue manager to restore the
  integrity of the two-phase-commit transaction.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.8
  v8.0       8.0.0.7
  v9.0 CD    9.0.2
  v9.0 LTS   9.0.0.2
  
  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:

Fix information

• Fixed component name

  WEBSPHERE MQ 7.

• Fixed component ID

  5724H7240

Applicable component levels