PM81457: EXTRA JMS REPORT MESSAGE GENERATED BY SIB WHEN MESSAGE DESTINATION IS WEBSPHERE MQ AND COA SPECIFIED.

8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Application sends a Java Message Service (JMS) request message
  with JMS properties set to request for Confirmation of Arrival
  (COA). Once the request message is sent,application waits on
  the local service integration bus(SIBus) reply-to-queue for a
  unique report message.
  
  SIB "intercepts" the message since the destination
  is a SIBus based remote destination linked with Websphere MQ
  (WMQ) queue manager. So SIB generates a report message that
  goes to the reply-to-queue.
  
  Once the message is received by the WMQ queue manager a second
  report message is generated by the WMQ and sent back to the
  reply-to-queue via MQ link.  The result being 2 COA messages
  where only one should be generated.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the default messaging provider     *
  *                  for IBM WebSphere Application Server        *
  *                  versions 8.0 and 8.5.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Duplicate report messages in the JMS    *
  *                      reply queue if the message flows        *
  *                      from SIB to WMQ and COA property set    *
  *                      for the message.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  As per the message flow described below, SIBus "intercepts"
  the message (Msg1) since the destination is a SIBus based
  remote destination linked with Websphere MQ (WMQ) queue
  manager. So SIB generates a report message (R1) that goes to
  the reply-to-queue.
  Once the message is received by the WMQ queue manager a second
  report message (R2) is generated by the WMQ and sent back to
  the
  reply-to-queue via MQ link.  The result being 2 COA messages
  where only one should be generated.
  Message flow:
  (Msg1)                (Msg1)
  Producer ----> ME  --> MQLink --> WMQ
  |                  |
  (R1) |            (R2)  |
  Reply Queue  <-----------
  R1   - report message produced by SIB.
  R2   - report message produced by WMQ.
  Msg1 - A message produced by producer application connected to
  local SIBus Messaging Engine (ME). This message has COA field
  and the name of of the reply queue (in reverse routing
  path field) set.
  

Problem conclusion

• Source code has been modified to ignore report message
  generation from SIBus if the SIBus remote destination is WMQ
  based destination.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.6 and the fix pack following 8.5.0.2.  Please
  refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WAS SIB & SIBWS

• Fixed component ID

  620800101

Applicable component levels

• R800 PSY

     UP