5db149e1fa
the current implementation of Start and End around the invocation of a Jax WS is asymmetric around the JAX-WS Handler Chain. Current behavior: (execution of incoming MessageHandlers) -> (TracingStartInInterceptor) -> (WebService Invocation) -> (execution of outgoing MessageHandlers) -> (TracingEndInInterceptor) if I understood the code of this cxf instrumentation correctly, the intent was to build the span close around the WebService Invocation (without Handler Chains). So the desired behavior would look like this: (execution of incoming MessageHandlers) -> (TracingStartInInterceptor) -> (WebService Invocation) -> (TracingEndInInterceptor) -> (execution of outgoing MessageHandlers) Unfortunately CXF is calling the Outgoing Chain inside the POST_INVOKE Phase of Cxf (so the outgoing chain is technically a sub-chain in the incoming chain... which is documented but quite surprising...). So the solution in the fix at least guarantees the the outgoing chain is invoked AFTER end of tracing. For any extra Interceptors in the POST_INVOKE Phase there is still no guarantee of ordering, but I think this is not a opentelemetry issue but a design-flaw of CXF... --------- Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com> Co-authored-by: Lauri Tulmin <ltulmin@splunk.com> |
||
|---|---|---|
| .. | ||
| jaxws-2.0/javaagent | ||
| jaxws-2.0-arquillian-testing | ||
| jaxws-2.0-axis2-1.6/javaagent | ||
| jaxws-2.0-common-testing | ||
| jaxws-2.0-cxf-3.0 | ||
| jaxws-2.0-metro-2.2/javaagent | ||
| jaxws-2.0-tomee-testing | ||
| jaxws-2.0-wildfly-testing | ||
| jaxws-common/javaagent | ||
| jaxws-jws-api-1.1/javaagent | ||