Wrong service file loaded in native mode after upgrading Mandrel from 23.0.1.2 JDK 17.8 to 23.1.0.0 JDK 21.0

[ppalaga]

Before the upgrade the service loader has loaded the resource META-INF/services/org.apache.cxf.bus.factory from the application runner quarkus-cxf-integration-test-mtom-awt-2.5.0-SNAPSHOT-runner.jar but now after the Mandrel upgrade, the resource is loaded from a dependency org.apache.cxf:cxf-core.

[ppalaga]

@zakkak @galderz is there any way to get back to the old behavior (which is BTW consistent with the JVM mode)?

[zakkak]

@ppalaga can you please provide a reproducer? It sounds like a GraalVM bug to me, but would need to have a look at it first.

[ppalaga]

Here is how to reproduce:

git clone git@github.com:quarkiverse/quarkus-cxf.git
cd quarkus-cxf
# the commit that upgrades to Quarkus 3.5.0
# there is a workaround in the main branch right after it, 
# so being at this particular commit is important
git reset --hard fea5378251d6aa98f6dad12dbbf4dc796d303e74
# build the whole source tree
mvn clean install -DskipTests -Dquarkus.build.skip -Denforcer.skip
# run some native test
cd integration-tests/mtom-awt
mvn clean verify -Pnative -Dquarkus.native.container-build
...
[ERROR]   MtomAwtIT>MtomAwtTest.uploadDownloadMtom

The root cause is that org.apache.cxf.BusFactory.getBusFactoryClass(ClassLoader) sees the default META-INF/services/org.apache.cxf.bus.factory from cxf-core rather than the one that we write into the application at build time (implemented around here )
And so the BusFactory loads the default implementation instead of our custom io.quarkiverse.cxf.QuarkusBusFactory

[zakkak]

The issue is introduced by oracle/graal@d5000f4 I will have a better look probably next week.

@olpaw FYI

[maxandersen]

This feels like a native image bug if not possible to have similar semantics as jvm?

[zakkak]

Correct

[zakkak]

The issue is introduced by oracle/graal@d5000f4 I will have a better look probably next week.

@olpaw FYI

Wrong mention... Sorry Paul. cc @chumer

[zakkak]

Upstream Graal fix: oracle/graal#7678

[zakkak]

The upstream fix has been merged and should land in GraalVM for JDK 22 and Mandrel 24.0. A backport request is pending to get the fix in GraalVM for JDK 17 and Mandrel 23.1 as well.

[ppalaga]

Thanks a lot, @zakkak!

[ppalaga]

I am closing this leaving the workaround in place.

[zakkak]

The upstream fix has been merged and should land in GraalVM for JDK 22 and Mandrel 24.0. A backport request is pending to get the fix oracle/graal#7957 (comment) and graalvm/mandrel#629.

FTR the upstream fix will land in land in GraalVM for JDK 21 and Mandrel 23.1 in the upcoming January CPU releases.