Adapter Subscriber activity in TIBCO ActiveMatrix BusinessWorks™ (BW) process would always receive duplicated messages from JMS Queue when BW Process restarted
book
Article ID: KB0089332
calendar_today
Updated On:
Products
Versions
TIBCO Adapter SDK
-
Not Applicable
-
Description
Resolution: Description: ========== In the case of using Adapter Publisher Service, Adapter Subscriber activity of TIBCO ActiveMatrix BusinessWorks™ (BW) process would always receive duplicated messages from JMS Queue when BW Process restarted every time.
Environment: ========== Adapter Subscriber activity with JMS Queue as transport type All supported versions of TIBCO Adapter SDK All supported versions of Adapter palette working with TIBCO ActiveMatrix BusinessWorks
Symptoms: ========= Adapter Subscriber activity of a BW process would always receive duplicate messages from the JMS Queue when the BW Process is restarted. From the JMS Queue, we can see the duplicated messages are cached and will not be released by the Queue.
Cause: ====== When using Adapter Subscriber activity with the JMS Queue transport, all messages received by Adapter Subscriber activity would not be confirmed by default, rather the JMS Queue tends to cache the messages until receiving the confirmation from consumer side.
Resolution: ========= In order to resolve this issue, we can change the default configuration for Adapter Subscriber activity. There are two ways to do so.
Solution 1: 1). In the BW process, go to the "Adapter Subscriber" activity, which is used for invoking Publisher Service.
2). Open the "Transport" tab from the "Adapter Subscriber" activity view.
3). Enable the "Auto Confirm" option.
Solution 2: 1). In the BW process, add a "Confirm" activity which is used for confirming message receiving - just following the "Adapter Subscriber" activity.
2). Open the "Configuration" tab from the "Confirm" activity view.
3). Select the target "ConfirmEvent" accordingly.
Issue/Introduction
Adapter Subscriber activity in TIBCO ActiveMatrix BusinessWorks™ (BW) process would always receive duplicated messages from JMS Queue when BW Process restarted