Ordered Delivery Send Port

[abirax]

HI ALL,
In one of our environment(Production). We had seen that one
of the SendPort set with ordered delivery was suspended and all the newer
incoming messages were getting queued up to this port. The Service Instance
was suspended as Suspended(non-resumable). We fixed it by deleting the
service instance.
However in our UAT environment. I can see that when the same port is
suspended(non-resumable). The messages don't queue up into the service
instance rather in the BizTalk admin console I can see one service instance
suspended(non-resumable) for each of the message I send in.
Can someone exaplin why this difference in behaviour both the ports are set
to ordered delivery in UAT and PRD and in both cases the send port displayed
the instance as suspended(non-resumable).
Thanks in Advance
Abir

[Faizel Khan]

Hi Abir

When you enable "Ordered Delivery" there is another option that is made
available, which is "Stop sending subsequent messages on current message
failure".
Basically it ensures that if a message in the queue fails all messages
behind it in the queue will not be sent.

It sounds like this option may not be enabled in your UAT environment, which
may account for every message being suspended.

- Faizel

Post by abirax
HI ALL,
In one of our environment(Production). We had seen that one
of the SendPort set with ordered delivery was suspended and all the newer
incoming messages were getting queued up to this port. The Service Instance
was suspended as Suspended(non-resumable). We fixed it by deleting the
service instance.
However in our UAT environment. I can see that when the same port is
suspended(non-resumable). The messages don't queue up into the service
instance rather in the BizTalk admin console I can see one service instance
suspended(non-resumable) for each of the message I send in.
Can someone exaplin why this difference in behaviour both the ports are set
to ordered delivery in UAT and PRD and in both cases the send port displayed
the instance as suspended(non-resumable).
Thanks in Advance
Abir

[abirax]

Hi Faizel,
Both the environments have the same configuration.
Regards
Abir

Post by Faizel Khan
Hi Abir
When you enable "Ordered Delivery" there is another option that is made
available, which is "Stop sending subsequent messages on current message
failure".
Basically it ensures that if a message in the queue fails all messages
behind it in the queue will not be sent.
It sounds like this option may not be enabled in your UAT environment, which
may account for every message being suspended.
- Faizel

Post by abirax
HI ALL,
In one of our environment(Production). We had seen that one
of the SendPort set with ordered delivery was suspended and all the newer
incoming messages were getting queued up to this port. The Service Instance
was suspended as Suspended(non-resumable). We fixed it by deleting the
service instance.
However in our UAT environment. I can see that when the same port is
suspended(non-resumable). The messages don't queue up into the service
instance rather in the BizTalk admin console I can see one service instance
suspended(non-resumable) for each of the message I send in.
Can someone exaplin why this difference in behaviour both the ports are set
to ordered delivery in UAT and PRD and in both cases the send port displayed
the instance as suspended(non-resumable).
Thanks in Advance
Abir