IBM Support

Changes to WebSphere JMS Front Side Handler drops messages

Troubleshooting


Problem

Configuration changes to the WebSphere JMS Front Side Handler while transactions are flowing might cause messages to be dropped when not using transactionality. The WebSphere JMS Front Side Handler must be referencing a WebSphere JMS Server configuration with transactionality disabled.

Cause

The previously configured WebSphere JMS Front Side Handler might receive the messages meant for the newly configured WebSphere JMS Front Side Handler. When the previous handler instance receives the message, it realizes it should not have received the messages, but does not have the capability to put the messages back on the destination for processing by the new instance.

Resolving The Problem

To prevent this issue, please follow these three steps if the WebSphere JMS Front Side Handler configuration has to be updated:

  1. Disable the WebSphere JMS Server instance referenced by the WebSphere JMS Front Side Handler
  2. Update the WebSphere JMS Front Side Handler configuration
  3. Enable the WebSphere JMS Server instance referenced by the WebSphere JMS Front Side Handler

[{"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"General","Platform":[{"code":"PF009","label":"Firmware"}],"Version":"5.0.0;6.0.0;6.0.1","Edition":"Edition Independent","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21671108

Page Feedback