[SLING-12326] SocketExceptions are no longer handled as error

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Engine 2.15.8, Engine 2.15.10, Engine 2.15.14
• Fix Version/s: Engine 2.15.16
• Component/s: Engine
• Assignee: Joerg Hoh
• Reporter: Joerg Hoh
• Created: 27/May/24 08:28
• Updated: 04/Jun/24 12:44
• Resolved: 27/May/24 10:08

Description

This commit 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.

Issue Links

• links to: GitHub Pull Request #47