You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2015/08/05 13:17:04 UTC
[jira] [Resolved] (SLING-4921) SlingMainServlet logs IOException at
debug level only
[ https://issues.apache.org/jira/browse/SLING-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-4921.
----------------------------------------
Resolution: Fixed
Patch applied in revision 1694179, with tests.
> SlingMainServlet logs IOException at debug level only
> -----------------------------------------------------
>
> Key: SLING-4921
> URL: https://issues.apache.org/jira/browse/SLING-4921
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.4.2
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Attachments: SLING-4921.patch, cae-stack-trace.txt
>
>
> The log level of IOException was reduced to DEBUG for SLING-3498, to avoid polluting the logs with client disconnect exceptions, which are hard to identify reliably.
> The downside is that this hides legit IOException from application code, as debug logs are usually not enabled on production systems.
> We should find a better to way to separate client disconnects from application-level IOException, and log the latter in the usual way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)