Reputation: 3707
We have a Mirth channel (synchronized) going to 4 destinations.
The first 3 destinations are web service calls (HTTP Sender) which are simply REST calls to get some basic data.
The 4th channel relies on the previous 3 destinations to have been completed cleanly. The data from those previous destinations are used in the 4th destination's transformer and the outgoing message is modified accordingly.
When the channel was initially released, the destinations were not set to "use persistent queues". Occasionally one of the web service calls would timeout. When this happens the content of the response (paraphrased) was "Error:HTTP Timeout....".
The channel was updated to use persistent queues. Now the response is "Message is queued".
In either case the 4th destination is called despite the result of previous destinations. And the response data is the Mirth error/warning message instead of data from the HTTP call.
What we need is for Mirth to queue on a destination and not continue until the destination has been successful.
Is this possible?
Thank you
Upvotes: 1
Views: 4407
Reputation: 134
For completeness, if anyone is looking for the answer to this, Mirth 3.x seems to be able to handle this case. ChronoFish received an answer to this on the Mirth forums. Even though it is a rather complex solution, a full example is provided in that answer.
Link to answer over at Mirth forums: http://www.mirthcorp.com/community/forums/showthread.php?t=9048
Upvotes: 1