…lient

Why:
On Conductor server side, an exception gets raised
`Failure in @ExceptionHandler com.netflix.conductor.rest.controllers.ApplicationExceptionMapper#handleAll(HttpServletRequest, Throwable)`.
Cause is attempting to write while the client aborted the connection
`org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe`, while the exception was wrapped in `ClosedChannelException`.

What:
Added a ClosedChannelException handler for such exceptions root caused by
ClientAbortException.

Testing done: Local run. Not trivial to emulate the issue in a test.
Such a test may rely on timing out the client before server responded.

Signed-off-by: Iva Avramova <ikoleva@vmware.com>

…lient

Why:
On Conductor server side, an exception gets raised
`Failure in @ExceptionHandler com.netflix.conductor.rest.controllers.ApplicationExceptionMapper#handleAll(HttpServletRequest, Throwable)`.
Cause is attempting to write while the client aborted the connection
`org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe`, while the exception was nested in `ClosedChannelException`.

What:
Added a ClosedChannelException handler for exception chain containing
ClientAbortException.

Testing done: Local run. Not trivial to emulate the issue in a test.
Such a test may rely on timing out the client before server responded.

Signed-off-by: Iva Avramova <ikoleva@vmware.com>

Signed-off-by: Iva Avramova <ikoleva@vmware.com>

Signed-off-by: Iva Avramova <ikoleva@vmware.com>

Ignoring a particular exception based on its stack trace
should be rather an alerting concern.

What:
Reverted ClientAbortedException specific handler.
Added test coverage for the existing exception handler.

Testing done: local run

Signed-off-by: Iva Avramova <ikoleva@vmware.com>