You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I attempted to re-send DLQ messages to a Queue. To accomplish this I went to the Details tab of a Queue and clicked the "Resend dead letter messages" icon at the bottom.
While it was running (and the status icon on the left nav was spinning) I clicked the X icon thinking I was just minimizing the status dialog. Instead it cancelled the task, and the result was all DLQ messages were lost.
Suggested enhancement:
As DLQ messages are resent, the following flow should be followed:
The individual DLQ message is peek-locked.
The message is attempted to be sent to the main queue.
Upon successful message send, the DLQ message is "completed."
Upon an error in the process, the lock is released.
The offending line is here, but it would require a refactor of the individual resend logic from read-and-delete entire batch > re-send to peek-lock individual message > attempt send > complete original message.
The text was updated successfully, but these errors were encountered:
Today I attempted to re-send DLQ messages to a Queue. To accomplish this I went to the Details tab of a Queue and clicked the "Resend dead letter messages" icon at the bottom.
While it was running (and the status icon on the left nav was spinning) I clicked the X icon thinking I was just minimizing the status dialog. Instead it cancelled the task, and the result was all DLQ messages were lost.
Suggested enhancement:
As DLQ messages are resent, the following flow should be followed:
The offending line is here, but it would require a refactor of the individual resend logic from read-and-delete entire batch > re-send to peek-lock individual message > attempt send > complete original message.
The text was updated successfully, but these errors were encountered: