--> Messages are processed NOW at the target.
NOT makes no sense :-)
In JBM 1.x duplicate detection specifically refers to duplicate detection on failover, i.e. a message sent before failover will not get sent again after failover.
It does not refer to more general duplicate detection on a non clustered server.
In JBM 2.0 we have more general duplicate detection that is designed for both the non clustered and clustered case.
For JBM 1.x if you are using dups_ok on your bridge, you can introduce your own duplicate detection at the application level at the point of consumption.