Cache filter should ignore ClientAbortException
-----------------------------------------------
Key: MAGNOLIA-3566
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3566
Project: Magnolia
Issue Type: Improvement
Components: cache
Affects Versions: 4.4.2, 4.3.8
Reporter: Danilo Ghirardelli
Assignee: Boris Kraft
I don't know if I'm the only one, but the cache module catches and logs this
exception:
java.lang.RuntimeException: ClientAbortException: java.net.SocketException:
Connection reset
at
info.magnolia.module.cache.filter.CacheFilter.doFilter(CacheFilter.java:159)
It's a quite common exception, that in most cases means the browser has closed
the connection. Ok, there are a few cases in which this may be useful to trace
borderline problems with https and internet explorer, but I'd really like to
have something to turn this off completely instead of having something harmless
cluttering log file at error level...
Disabling the log completely for the cacheFilter class is not a good idea, and
using the log4j extras to filter out a single exception isn't a good solution
either.
The exception re-thrown from this filter is wrapped in a runtime exception, so
it's not even immediate to catch and ignore those exceptions in another filter
in the chain.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
