You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/03/05 15:33:42 UTC
[jira] [Commented] (QPID-5602) reduce severity and improve
IOException logging in IoSender
[ https://issues.apache.org/jira/browse/QPID-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920890#comment-13920890 ]
ASF subversion and git services commented on QPID-5602:
-------------------------------------------------------
Commit 1574506 from [~gemmellr] in branch 'qpid/trunk'
[ https://svn.apache.org/r1574506 ]
QPID-5602: change log level to info, include socket address in message, report only the exception type and message rather than logging full stackrace
> reduce severity and improve IOException logging in IoSender
> -----------------------------------------------------------
>
> Key: QPID-5602
> URL: https://issues.apache.org/jira/browse/QPID-5602
> Project: Qpid
> Issue Type: Bug
> Components: Java Common
> Affects Versions: 0.26
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.27
>
>
> IoSender emits an error message and a logs a Stacktrace when it exits due to an IoException, e.g due to a remote application being abruptly stopped.
> Any issues stemming from the thread exiting result in their own exceptions being thrown and/or log messages being produced, so this logging is often duplicate and is typically not indicative of a problem needing intervention, it should be reduced in severity. It should also be improved to include the socket address, and remove the stacktrace which adds little benefit in this case and simply leads to unecessary confusion.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org