Have Geek Brain

Handling failures from MSMQ in BizTalk by resubmitting

Does anyone have any pointers to good practices / potential projects for handling the situation in BizTalk orchestration, the response from the long term service failed, so the initiation message should be re-sent

I have a situation where orchestration sends a message to an MSMQ queue and then waits for a response on another queue. The response time should now be less than a minute, but the "service" on the other end of the queue sometimes fails ...
and that's not something I control, so I can't change / fix it

Is there some design pattern I can use in BizTalk to timeout and send an initiation message?

0


a source to share


2 answers


the BPEL standard defines a "Pick" action and BizTalk has a "Listen" form for that so you can basically define a wait period for your receive activity in the response queue after that you might want a boolean flag to decide whether to loop back / repeat or receive and therefore the business process continues.



+1


a source


  • Define one orchestration that can be used to resend messages, these messages to be queued are fetched from the message box.

  • If the response from the response queue is delayed, use a singleton loop to discard the message.

Side note: You may need to enable the DSN property on your dispatch port, just to listen for any exceptions you may have.



Refer to article ...

BizTalk Orchestration Exception Handling

0


a source






More articles:


All Articles