Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect logging when Retries are disabled #2094

Closed
SimonCropp opened this issue May 5, 2014 · 3 comments
Closed

Incorrect logging when Retries are disabled #2094

SimonCropp opened this issue May 5, 2014 · 3 comments
Assignees
Labels
Milestone

Comments

@SimonCropp
Copy link
Contributor

When both SLR and FLR are disable the logging is incorrect in two ways

  • Incorrectly reports that FLR has failed when no retry was done
2014-05-06 08:34:09.544 +10:00 [Error] Message with '"9320cdcc-6f7a-41c0-a046-a323008d3352"' id has failed FLR and will be moved to the configured error queue.
  • Exception is reported as Info and error does not contain exception information

There are two log entries. The first one is an info which actually contains the exception details. The second is an error which does not contain the exception details. This is problematic because if the user is only monitoring warnings and above (a common scenario) they will not be able to see the exception information.

2014-05-06 08:34:09.472 +10:00 [Information] Failed to process message System.Exception: Foo .....
2014-05-06 08:34:09.544 +10:00 [Error] Message with '"9320cdcc-6f7a-41c0-a046-a323008d3352"' id has failed FLR and will be moved to the configured error queue.

Repro here https://github.com/Particular/BugsRepro/tree/master/DisabledRetryRepro

@SimonCropp SimonCropp added this to the 5.0.0 milestone May 5, 2014
@SimonCropp SimonCropp added the Bug label May 5, 2014
@SimonCropp SimonCropp changed the title Incorrect logging when Retries are enabled Incorrect logging when Retries are disabled May 8, 2014
@SimonCropp SimonCropp modified the milestones: 5.1.0, 5.0.0 Jun 2, 2014
@SzymonPobiega SzymonPobiega self-assigned this Sep 30, 2014
@SzymonPobiega
Copy link
Member

Confirmed that the message gets to the error queue so according to @johnsimons this is the expected behaviour. The info message about failing FLR needs to be changed however.

@SzymonPobiega
Copy link
Member

Fixed in #2434

@SzymonPobiega
Copy link
Member

Fixed via f2152aa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants