When the WebSphere Transformation Extender Launcher is listening for a Topic message using the JMS Adapter, two trigger events may occur for every one message posted.
In the Management Console or the Event Monitor, it can be seen that two maps run for every single trigger. When the output content and audit logs are reviewed, it can be seen that only one trigger is able to successfully retrieve the message content and the other trigger receives 0 bytes.
This has been identified as a product defect under APAR PM82088
This issue can affect a Launcher JMS Adapter listener when connecting to any JMS Messaging server.
Diagnosing the problem
Two outputs are produced received for every one JMS message received.
Resolving the problem
Apply fix for APAR PM82088