You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/07/09 07:26:00 UTC
[jira] [Commented] (WICKET-6565) ResponseIOException logged as an
error in DefaultExceptionMapper
[ https://issues.apache.org/jira/browse/WICKET-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16536607#comment-16536607 ]
ASF subversion and git services commented on WICKET-6565:
---------------------------------------------------------
Commit 58c0dcf6c01ce9d0acdc514c7bb54032485b01ec in wicket's branch refs/heads/wicket-8.x from [~svenmeier]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=58c0dcf ]
WICKET-6565 connection lost is not an error
logging with debug is sufficient
> ResponseIOException logged as an error in DefaultExceptionMapper
> ----------------------------------------------------------------
>
> Key: WICKET-6565
> URL: https://issues.apache.org/jira/browse/WICKET-6565
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 8.0.0, 6.28.0
> Reporter: Daniel Stoch
> Assignee: Sven Meier
> Priority: Minor
>
> DefaultExceptionMapper handles by default some "internal" exceptions. ResponseIOException is one of them, but when this kind of exception occurs then an error is logged in DefaultExceptionMapper.mapExpectedExceptions(...):
> {code}
> Â logger.error("Connection lost, give up responding.", e);
> {code}
> Why it is logged as an error, which means something is wrong in our application? If it is
> handled transparently by a framework then it should not be logged as error.
> Maybe it should be logged as debug or warning? Maybe we don't need the stacktrace either.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)