Test Failure: com.ibm.ws.testing.opentracing.test.FATOpentracing.testImmediate

[fmhwong]

RTC 270522

testImmediate:junit.framework.AssertionFailedError: EQ [ Operation ] expected:<[GET:com.ibm.ws.testing.opentracing.service.FATOpentracingService.]getTracerState> but was:<[http://localhost:8010/serviceApp/rest/testService/]getTracerState>
at com.ibm.ws.testing.opentracing.test.FATOpentracing.assertEq(FATOpentracing.java:211)
at com.ibm.ws.testing.opentracing.test.FATOpentracing.verifyTracerStateEvent(FATOpentracing.java:615)
at com.ibm.ws.testing.opentracing.test.FATOpentracing.verifyTracerStateEvent(FATOpentracing.java:597)
at com.ibm.ws.testing.opentracing.test.FATOpentracing.verifyTracerStateEvent(FATOpentracing.java:591)
at com.ibm.ws.testing.opentracing.test.FATOpentracing.testImmediate(FATOpentracing.java:657)
at componenttest.rules.repeater.RepeatTests$CompositeRepeatTestActionStatement.evaluate(RepeatTests.java:115)

[lamkavan]

After careful analysis by Felix Wong, the root cause of this issue is caused by a synchronization problem found within the implementation of opentracing1.x. PR to resolve issue is here #10442

In the implementation there is
protected void activate(ComponentContext context)
and
protected void setOpentracingFilterHelper(OpentracingFilterHelper helper)

These two methods needs to be synchronized such that they do not both run at the same time. If these methods run at the same time it can result in the helper for either the Container or Client filter to be NULL when using MicroProfile OpenTracing.