PM82088: DOUBLE TRIGGERING MAY OCCUR WHEN THE LAUNCHER IS CONFIGURED TO USE THE JMS ADAPTER AND THE SOURCE EVENT IS A TOPIC

APAR status

• Closed as program error.

Error description

• This issue may be observed when using the IBM WebSphere
  Transformation Extender JMS adapter to watch for a particular
  Topic.
  
  A Topic is used to identify a particular set of data in a
  publish.subscribe scenario, where WTX is the subscriber in this
  instance.
  
  Instead of one map execution for every post, a double trigger is
  observed.  Audit logs reveal that only one of the maps received
  any data and the 'other' map received 0 bytes.
  

Local fix

• WTXCQ - WTX00042198
  PB / PB
  Circumvention: The map could be configured to not continue if
  the input is 0 bytes.
  

Problem summary

• Users Affected:
  IBM WebSphere Transformation Extender JMS Adapter users that
  listen on a given JMS Topic.
  
  Problem Description:
  The JMS Adapter Listener is notifying the Launcher twice for the
  same event.
  
  Platforms Affected:
  All
  

Problem conclusion

• The JMS listener only submits one trigger notification for a
  watched topic.  Before this fix, two notifications were getting
  sent, which incorrectly caused a 2nd map to run against the same
   message id.  Also, verbose tracing has been enabled in order to
   capture additional details when attempting to diagnose problems
   with the JMS listener.
  
  Delivered in:
  8.3.0.6, 8.4.0.4
  

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 LAUNC

• Fixed component ID

  5724M4011

Applicable component levels

• R820 PSY

     UP

• R830 PSY

     UP

• R840 PSY

     UP