You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (Jira)" <ji...@apache.org> on 2020/01/15 10:24:01 UTC
[jira] [Closed] (CXF-8169) CXF opentracing - Span#finish is never
called in case of client timeouts
[ https://issues.apache.org/jira/browse/CXF-8169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh closed CXF-8169.
------------------------------------
> CXF opentracing - Span#finish is never called in case of client timeouts
> ------------------------------------------------------------------------
>
> Key: CXF-8169
> URL: https://issues.apache.org/jira/browse/CXF-8169
> Project: CXF
> Issue Type: Bug
> Components: Tracing
> Affects Versions: 3.2.11, 3.3.4, 3.4.0
> Reporter: Baptiste AIGLIN
> Assignee: Andriy Redko
> Priority: Major
> Fix For: 3.4.0, 3.3.5, 3.2.12
>
> Attachments: cxf-reproducer.tar.gz
>
>
> While using the CXF opentracing feature with any CXF client, we see that in case of connectionTimeout or receiveTimeout the span#finish is never called by the OpenTracing client interceptors. We can clearly see that inside the OpenTracingClientStartInterceptor from the OpenTracingClientFeature there is no handleFault() method defined to handle such case.
> I wrote the test allowing to reproduce this behavior using a JAX-RS client and a really simplistic fix on the CustomOpenTracingClientFeature where the current OpenTracingClientStartInterceptor is overriden in order to add such handleFault method and using the OpenTracingClientStopInterceptor#handleMethod in order to trigger the stop.
> Thanks in advance for your feedback.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)