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

Logging does not seem to kick in early enough #274

Closed
mookid8000 opened this issue Nov 19, 2014 · 2 comments
Closed

Logging does not seem to kick in early enough #274

mookid8000 opened this issue Nov 19, 2014 · 2 comments

Comments

@mookid8000
Copy link
Member

Check out this question on StackOverflow - it claims that an error in the configuration is not logged to the log file.

It should be logged to the file.

(if you're logging to a log file)

@jrossstocholm
Copy link

FYI: I have configured log4net with a RollingFileAppender and a ConsoleAppender ... and it doesn't appear in neither :-)

@mookid8000
Copy link
Member Author

I remember now that this behavior is intentional!

The thing is that logging is introduced in the first place because you will not be around to catch any exceptions that might happen.

At application startup, though, the time where you initialize all kinds of stuff, you should always catch exceptions and log them and probably refuse to start up.

If Rebus would log exceptions that also surface to the caller, it would not be clear whose responsibility it was to the log the exception.

I hope that makes sense :)

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

No branches or pull requests

2 participants