fix order of cxf handlers to enable symmetric tracing around jaxws handler chain (#8160)

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>
This commit is contained in:
pellmont 2023-04-03 12:06:51 +02:00 committed by GitHub
parent 8c7a8e1dfb
commit 5db149e1fa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 18 additions and 0 deletions

View File

@ -5,6 +5,7 @@
package io.opentelemetry.javaagent.instrumentation.cxf;
import org.apache.cxf.interceptor.OutgoingChainInterceptor;
import org.apache.cxf.message.Message;
import org.apache.cxf.phase.AbstractPhaseInterceptor;
import org.apache.cxf.phase.Phase;
@ -12,6 +13,8 @@ import org.apache.cxf.phase.Phase;
public class TracingEndInInterceptor extends AbstractPhaseInterceptor<Message> {
public TracingEndInInterceptor() {
super(Phase.POST_INVOKE);
// end the span before the OutInterceptors (callbacks) are executed
addBefore(OutgoingChainInterceptor.class.getName());
}
@Override

View File

@ -4,7 +4,13 @@
*/
import hello.HelloServiceImpl
import io.opentelemetry.api.trace.Span
import io.opentelemetry.context.Context
import io.opentelemetry.instrumentation.api.instrumenter.LocalRootSpan
import org.apache.cxf.jaxws.EndpointImpl
import org.apache.cxf.message.Message
import org.apache.cxf.phase.AbstractPhaseInterceptor
import org.apache.cxf.phase.Phase
import org.apache.cxf.transport.servlet.CXFNonSpringServlet
import javax.servlet.ServletConfig
@ -18,5 +24,14 @@ class TestWsServlet extends CXFNonSpringServlet {
Object implementor = new HelloServiceImpl()
EndpointImpl endpoint = new EndpointImpl(bus, implementor)
endpoint.publish("/HelloService")
endpoint.getOutInterceptors().add(new AbstractPhaseInterceptor<Message>(Phase.SETUP) {
@Override
void handleMessage(Message message) {
Context context = Context.current()
if (LocalRootSpan.fromContext(context) != Span.fromContext(context)) {
throw new IllegalStateException("handler span should be ended before outgoing interceptors")
}
}
})
}
}