Joerg Hoh created SLING-12326:
---------------------------------
Summary: SocketExceptions are no longer handled as error
Key: SLING-12326
URL: https://issues.apache.org/jira/browse/SLING-12326
Project: Sling
Issue Type: Task
Components: Engine
Affects Versions: Engine 2.15.14, Engine 2.15.10, Engine 2.15.8
Reporter: Joerg Hoh
[This
commit|https://github.com/apache/sling-org-apache-sling-engine/commit/8ab96759cd435520a228271fbbb9d37955954c80]
introduced a special handling for SocketExceptions under the assumptions that
the only Socket Exceptions can happen when Sling/Jetty fails to stream back the
response to the client (browser).
But there are other types of SocketExceptions, which can happen during page
rendering, e.g. when a Servlet/Script does connections on its own, for example
to fetch data from a backend system. If these exceptions are wrapped and
thrown, it could lead to a situation, that the error handling in this place is
actually not kicking in at all, and also no logging for this exception is done
at all.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
