Client instrumentation does not finish spans after ConnectionException

[mabn]

It seems that ClientTracingFilter.filter(request, response) is not called after:
javax.ws.rs.ProcessingException: java.net.ConnectException: Connection refused (Connection refused)

ClientRuntime.invoke from jersey client:

    public ClientResponse invoke(final ClientRequest request) {
        ClientResponse response;
        try {
            try {
                response = connector.apply(addUserAgent(Stages.process(request, requestProcessingRoot), connector.getName()));
            } catch (final AbortException aborted) {
                response = aborted.getAbortResponse();
            }

            return Stages.process(response, responseProcessingRoot);
        } catch (final ProcessingException pe) {
            throw pe;
        } catch (final Throwable t) {
            throw new ProcessingException(t.getMessage(), t);
        }
    }

The exception is thrown from the line with response = conn... and the execution skips over Stages.process(response, responseProcessingRoot) which would run the filter.

Maybe there is some other mechanism which can react to this exception.

[mabn]

Oh, it's already reported under #30
I'm closing this.

Although not being able to handle exceptions will leave ScopeManager with a scope opened by the request filter.