Hi All,

We were facing duplicate documents problem with the trigger ,then we switched the exactly once button on and the history time to live to 15 mins but still we are facing some duplicate documents,how is it possible ....I want to stop these documents at the broker level itself how to proceed on this?

Please reply as this has been a crucial issue for us.

Thanks in advance

A document received from the broker can have a value of 'new' 'duplicate' or 'in doubt'. IS will use the following logic to determine the status:  DB history -> resolver service -> redelivery count

When you enable exactly once processing by setting detect duplicates property for a trigger to true; these 3 methods are used to identify how many times a document has been received from the broker and processed. These are:
Document history db: this records the service execution for a particular document, if a document has been received before and the service has completely been executed the db will contain a processed status of "completed"

Document resolver service: a custom service you can write to check if the document has previously been processed. E.g. if you are receiving orders from the broker, you might want to check for the order id in the db. If the order id exists you then know it has been processed.

Redelivery count: number of times the document has been sent as maintained by the broker, it should be 0 for the very first document and  increase on subsequent deliveries. Note that earlier versions of the broker server&e.g. v6 does not maintain the delivery count.

I assume in this case there is no DB history or a resolver service and redelivery count is not maintained for the document, i.e. you are using an old broker server, v6?