You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "galderz (via GitHub)" <gi...@apache.org> on 2026/05/04 14:50:55 UTC
Re: [I] Intermittent native build failures due to java.util.concurrent.ForkJoinWorkerThread$InnocuousForkJoinWorkerThread was found in the image heap [camel-quarkus]
galderz commented on issue #8344:
URL: https://github.com/apache/camel-quarkus/issues/8344#issuecomment-4372033209
FYI @ppalaga et al
At a glance, I don’t think the original issue of https://github.com/quarkiverse/quarkus-cxf/issues/1856 (Arc +java.lang.Thread) is the same as this InnocuousForkJoinWorkerThread + Charset. You might be able to workaround it by making `java.nio.charset.Charset.ThreadTrackHolder` runtime initialized but that might have other consequences. The first I'd suggest doing is enabling `-H:+PrintClassInitialization` and looking at what the initialization configuration + report is for `java.nio.charset.Charset` and `java.nio.charset.Charset.ThreadTrackHolder` classes. Also, the class initialization configuration + report output can help you see if your configuration is having an effect.
One more thing you can do is run CI with additional native image parameter `--trace-object-instantiation=java.util.concurrent.ForkJoinWorkerThread$InnocuousForkJoinWorkerThread` so that if it happens again we can see at least one of the potential avenues for instantiating it.
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org