Why are many messages not processed/confirmed when mulitple adapter instances are running in DQ mode?

Why are many messages not processed/confirmed when mulitple adapter instances are running in DQ mode?

book

Article ID: KB0088729

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel -
Not Applicable -

Description

Resolution:
Issue
-------
When TIBCO Adapter for Siebel is configured with Inbound services(Subscription or Request Response Services) with RVCMQ transport, many  messages are not processed/confirmed.

Reason
----------
This happens if there are zombie adapter instances which are picking up the messages.

Resolution
-------------
When stopping adapter instances please make sure that the adapter instnaces are gracefully shutdown and there are no zombie "adsbl" processes on the OS.
Adapter instances can be gracefully shutdown by:
1) Sending a message on the stop subject/topic. This can be configured in the General Tab at the adapter instance level.
2) Invoking 'stopAdapterInstance()' hawk method of the adapter. For this the GV 'HawkEnabled' should be True and adsbl.perfMon should be set to 'on'.
When multiple adapter instances are stopped/restarted please make sure that the adapter processes are removed properly.

Environment
----------------
All

Issue/Introduction

Why are many messages not processed/confirmed when mulitple adapter instances are running in DQ mode?