Incorrect classloader used by common ForkJoinPool when using Executable Jar

[pcimcioch]

Incorrect classloader used by common ForkJoinPool when using Executable Jar

[philwebb]

See #19427 for some previous discussion on this topic.

[philwebb]

We're going to investigate if we can provide our own ForkJoinWorkerThreadFactory and possibly configure the system property by default. If we do this, we'll also need a way to opt-out of our version.

[Sasivarnan1988]

I am having the same issue even while using the completable future without executors. I tried custom thread factory and set that through environment variable but still I could see jdk loader incorrect one. Any help? This is on Jdk17

[wilkinsona]

@Sasivarnan1988 A correctly configured thread factory should resolve the problem. If that isn't working for you, please follow up on Stack Overflow. As mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements.

[pcimcioch]

@Sasivarnan1988
The problem with custom thread factory is that java uses "system classloader" to instantiate it. And your application classes are not availabe in system class loader. It may be hard to notice, as it will fail silently.
You would have to somehow pack your custom thread factory together with the launcher code in the jar, which I'm not sure is possible using gradle/maven spring boot plugin

[wilkinsona]

It's reasonably straightforward with Gradle but much harder with Maven. See #6626.

[Sasivarnan1988]

Thank you all for the comments. I will post it in the stack overflow as I have few more doubts on this.