I developed WCF DeadletterQueue service to handle fault tolerance. This service picks up messages from deadletterqueue and sends them to a different endpoint. Now problem is, even though this new endpoint is also down, deadletterqueue service puts
the message into journel (means marks it processed), at the other end, the message remains in the queue of new end point. This hurts reliability of WCF MSMQ, client thinks that he submitted message but as service is down, message lies in the queue without
processed. I tried to specify a CustomDeadletterQueue in the client configuration of this DeadletterQueue service, and pointed that customdeadletterqueue to the same deadletter queue the service is working for. But it doesn't work out.
Appreciate if any idea or solution.
View Complete Post