JiriOndrusek opened a new issue, #9200:
URL: https://github.com/apache/camel-quarkus/issues/9200
### Bug description
`SedaVirtualThreadsIT.sedaExecutesOnVirtualThread` (foundation-grouped,
native group-03) fails on the `camel-main` branch since the tests were
re-enabled by #9189.
```
Expected: a string containing "java.lang.VirtualThread"
Actual: java.lang.Thread
```
CI run: https://github.com/apache/camel-quarkus/actions/runs/35573093554
The same test passes on `main`. The difference is the Camel artifact, not
the Camel code: `main` uses the released Camel jars (built on JDK 25,
`Multi-Release: true`, containing
`META-INF/versions/21/.../CamelThreadFactory.class`), while the camel-main CI
builds Camel from source on JDK 17. Camel compiles its Java 21/25 sources only
through JDK-activated profiles (`java-21-sources`, `java-25-sources` in
[core/camel-util/pom.xml](https://github.com/apache/camel/blob/main/core/camel-util/pom.xml)),
so the JDK 17 build produces a jar with the base
[CamelThreadFactory](https://github.com/apache/camel/blob/main/core/camel-util/src/main/java/org/apache/camel/util/concurrent/CamelThreadFactory.java)
only, which always creates platform threads. The virtual-thread variant lives
in
[src/main/java21](https://github.com/apache/camel/blob/main/core/camel-util/src/main/java21/org/apache/camel/util/concurrent/CamelThreadFactory.java).
Reproduced locally: with camel-util built on JDK 25 the native IT passes;
with the two profiles disabled (equivalent to a JDK 17 build) it fails with the
CI message. The nightly `camel-master-cron.yaml` builds Camel on JDK 17 as well.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
