PM68448: INCLUDE THE THREAD NAME IN THE BIP2124E & BIP2121E MESSAGES

WebSphere Message Broker V8.0 - Fix Pack 8.0.0.2

APAR status

• Closed as program error.

Error description

• When Message Broker encounters a problem committing or
  rolling back a transaction it throws a restart exception
  which is caught by the thread bootstrap code and
  initiates a restart. When a restart exception is caught
  by the thread bootstrap code it issues a BIP2124E or
  BIP2121E message indicating that an error requiring a
  restart has been caught. At the moment this message does
  not contain the message flow/thread name so it is hard to
  work out what message flow/thread the error has
  occurred on. This APAR will enhance these messages to
  log out the message flow/thread name details.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker who encounter un-handled
  exceptions that are caught by the thread bootstrap code.
  
  
  Platforms affected:
  MultiPlatform, z/OS
  
  ****************************************************************
  PROBLEM SUMMARY:
  When an un-handled exception is caught by the thread bootstrap
  code it prints out a BIP2124E or BIP2121E message indicating
  that an exception has been caught and the details of this
  exception. If the exception does not contain any details about
  the message flow or thread that caused that exception then it
  can be very difficult to work out where this exception was
  generated. This APAR will enhance these messages to log out
  the message flow/thread name details.
  A similar problem can also be seen in abend situations when a
  ".abend" file is written and this does not always include the
  message flow or thread name. This APAR will also enhance the
  abend handling code to include the message flow/thread name in
  the ".abend" file.
  

Problem conclusion

• WebSphere Message Broker has been modified to store away the
  name of all threads on thread startup so that it can be logged
  by the thread bootstrap code when an un-handled exception is
  caught and printed out in any ".abend" files generated by an
  abend.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Platform           v7.0
  --------           --------------------
  Multiplatforms     7.0.0.6
  
  Platform           v8.0
  --------           --------------------
  Multiplatforms     8.0.0.2
  
  The latest available maintenance can be obtained from
  'WebSphere Message Broker Recommended Fixes'
  http://www.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available, information on
  its planned availability can be found in 'WebSphere Message
  Broker Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

  WEB MB Z/OS

• Fixed component ID

  5655V6000

Applicable component levels

• R700 PSY

     UP