The transaction that led to a TimeoutControl that led to the TimeoutNotification? Not likely.
I agree, since it landed on a queue (SYSTEM.BROKER.TIMEOUT.QUEUE) that transaction ended.
mqjeff wrote:
The transaction that started when the TimeoutNotification node fired? Are you sure it doesn't?
Yes I'm fairly sure. An error is thrown but the message uncomfortably disappears. As it came from a general queue (S.B.T.Q), I'd prefer if it ended up on the DLQ.
As it came from a general queue (S.B.T.Q), I'd prefer if it ended up on the DLQ.
It would have to be a persistent message for it to end up on the DLQ.
Are you sure about this? It sounds odd and the documentation mentions nothing of it. I also tried setting message persistence for the message without any success backing out the message.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum