Unit test DefaultJobClassNameProviderTest#assertGetLambdaJobName fails on OpenJDK 21

[linghengqian]

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

• Searched open and closed GitHub issues.
• Read documentation: ElasticJob Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ElasticJob did you use?

• 0b3a6eb

Expected behavior

• Unit test DefaultJobClassNameProviderTest#assertGetLambdaJobName executes successfully on JDK 21.

Actual behavior

• Unit test DefaultJobClassNameProviderTest#assertGetLambdaJobName fails on JDK 21. Refer to Support for building with OpenJDK 21 #2270 .

Reason analyze (If you can)

• There is currently no solution. I'm still not sure what causes this unit test to fail on OpenJDK 21, and I can't find the corresponding JEP change.

Steps to reproduce the behavior.

• Null.

Example codes for reproduce this issue (such as a github link).

• Refer to https://github.com/apache/shardingsphere-elasticjob/blob/0b3a6eb993ee1abcb8ae81efa6ccaeb9b494ea5c/kernel/src/test/java/org/apache/shardingsphere/elasticjob/kernel/internal/setup/DefaultJobClassNameProviderTest.java .

@Test
@DisabledForJreRange(min = JRE.JAVA_21, max = JRE.OTHER)
void assertGetLambdaJobName() {
    JobClassNameProvider jobClassNameProvider = new DefaultJobClassNameProvider();
    FooJob lambdaFooJob = shardingContext -> {
    };
    String result = jobClassNameProvider.getJobClassName(lambdaFooJob);
    assertThat(result, is("org.apache.shardingsphere.elasticjob.kernel.internal.setup.DefaultJobClassNameProviderTest$$Lambda$"));
}

[linghengqian]

• This unit test previously executed successfully on a GraalVM Native Image built with GraalVM CE 23.1.0 For JDK 21, but failed under the Hotspot JDK. As merged in [GR-47937] Make lambda class names format consistent with the JDK name format oracle/graal#7775 , this unit test fails in GraalVM Native Image built with GraalVM CE 24.0 For JDK 22 like Hotspot JDK.

• I'm still not sure what we should do on this issue, there is an unknown JEP that breaks unit test execution.

[linghengqian]

• I am working on the current issue.

[linghengqian]

• Waiting for https://forums.oracle.com/ords/apexds/post/why-did-the-class-name-of-the-lambda-class-change-starting-7639 .