Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Added message timeout tracking to the ErrorTracker #73
When a message has been tracked for some TimeSpan the message is removed in order to ensure it doesn't leak due to the TimeToBeReceived being expired. Maybe a future change should let the timeout be dependent on the Headers.TimeToBeReceived since it doesn't really make any sense to remove error-tracking on messages which time to be received hasn't been exceeded.
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
Given that retries will occur in very quick succession, it would probably work even with much shorter expiration on the retry tracker.
If a retry tracker were to expire before the final retry, it would mean that the message processing took almost 5 hours with 5 retries and an expiration of 24 hours. Therefore: No worries :)