-
Notifications
You must be signed in to change notification settings - Fork 992
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
Adjust logging when running into Exceptions (exceptionCaught()) #140
Labels
type: feature
A new feature
Milestone
Comments
mp911de
changed the title
Adjust logging when running into Exceptions (
Adjust logging when running into Exceptions (exceptionCaught())
Sep 24, 2015
exceptionCaught()
)
mp911de
added a commit
that referenced
this issue
Oct 1, 2015
- Log consumed exceptions at DEBUG level consumed means either the exception was attached to a command or it was stored in the connection error field when disconnected - Log timeout/connection reset/broken pipe IOExceptions on DEBUG level and log all other IOExceptions on INFO level - Keep: Everything else is logged on WARN level - Adopt log pattern/log behavior to write log listener
Needs merge to 4.1 |
mp911de
added a commit
that referenced
this issue
Oct 3, 2015
- Log consumed exceptions at DEBUG level consumed means either the exception was attached to a command or it was stored in the connection error field when disconnected - Log timeout/connection reset/broken pipe IOExceptions on DEBUG level and log all other IOExceptions on INFO level - Keep: Everything else is logged on WARN level - Adopt log pattern/log behavior to write log listener
mp911de
added a commit
that referenced
this issue
Oct 8, 2015
- Log consumed exceptions at DEBUG level consumed means either the exception was attached to a command or it was stored in the connection error field when disconnected - Log timeout/connection reset/broken pipe IOExceptions on DEBUG level and log all other IOExceptions on INFO level - Keep: Everything else is logged on WARN level - Adopt log pattern/log behavior to write log listener
Implemented. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When exception in the channel pipeline processing occurs, the
exceptionCaught()
method is called. Depending on the state (connected/disconnected, command in the queue) the exception is:WARN
levelChange:
IOException
s with the reasons (check for the correct text)connection reset by peer
andconnection timed out
occur, log them onDEBUG
level, everything else onWARN
levelReference: mp911de/spinach#12
The text was updated successfully, but these errors were encountered: