TCK Challenge ContextPropagationTests#testContextualFunction, JNDI search in unchanged APPLICATION context

[aubi]

Specification:

Jakarta Concurrency 3.0.0

Challenged test(s):

ee.jakarta.tck.concurrent.spec.ContextService.contextPropagate.ContextPropagationTests#testContextualFunction

TCK version:

3.0.1

Tested implementation:

Payara 6 (branch)

Description

Similar situation to #224, the test should set APPLICATION to be cleared, but it is in unchanged. It then tests JNDI lookup for java:module and expects, that it is not available. For some servers, the current thread can be created from a servlet thread and inherits its invocation, e.g. the JNDI context is available and the test fails.

I will prepare a fix for the test.

[njr-11]

Reassigned to @smillidge per TCK process which says that challenges are to be resolved by the specification project lead. I added a thumbs up to the description to indicate that I'm in favor of accepting this challenge.

[dmatej]

It is a bit confusing if this is resolved OR there is a plan to fix the test - or to delete it. It seems the challenge was accepted, so I guess this issue should be already closed?

[KyleAure]

Currently, these tests are still disabled via this challenge.
I think the issue should stay open until the tests are fixed.

To me this seems like just a test bug, and not anything that is unclear in the specification.
Correct me if I am wrong on that.

I've assigned this issue to the 3.2.0 milestone to get this resolved for EE 12.

[aubi]

@dmatej @KyleAure The plan is to finish the PRs I opened. The issue is a different way the thread factory is created and therefor different expectation about the thread context. Also, confusion between thread context and EJB context needs to be cleared.
But to explain it clearly, I need to finish my PRs...