Description:
Symptoms
========
The Remedy Adapter in a pub-sub scenario publishes two identical messages for every record inserted.

Impact
======
Loss of Functionality.
TIB_PENDING_NOTIFICATIONS table gets two identical tuples for every record created by a Subscriber/ BMC Remedy GUI.

Workaround
==========
Remove one filter (the one which is not being used) or disable the publication for Submit/Modify on that object in the particular filter.

Cause
=====
The presence of both 510 and the 520 adapter working on the same Remedy AR Server setup. This means two filters namely TIB:ADREMEDY5.1.0/AR/FILTER and TIB:ADREMEDY5.2.0/AR/FILTER were both active on the same business object on both Submit and Modify.

Resolution
==========
N/A since this is an issue of configuration at the application end.
Symptoms:

Cause:

The Remedy Adapter in a pub-sub scenario publishes two identical messages for every record inserted.