Closed jpmsilva closed 6 months ago
I think this can be closed now? It's part of the 1.5 release
@mkurz Thank you for following up.
Apologies for the spam in advance. I just wanted to confirm that the fix does indeed work, and we no longer observe the illegal access exception when starting the application with version 1.5. I also wanted to leave a word of thanks for the wonderful libraries that you provide to the community, and the amazing support and maintenance to them. I really enjoyed learning from the multijar release commit you provided, as I had never seen it actually done in a project. Thank you!
We always run our application with JDK21 and
-Dsun.reflect.debugModuleAccessChecks=true
to check for possible issues resulting from module boundary issues. After recently upgrading logback, we started seeing this exception being logged:Now, while the class
ExecutorServiceUtil
catches that exception and handles it, it also points to an underlying issue: thegetMethod(FACTORY_METHOD_NAME)
is performed on the wrong (concrete) classjava.lang.ThreadBuilders.VirtualThreadBuilder
, instead of the public interfacejava.lang.Thread.Builder
.As such, I can't see any way the current code would work as is.
I hope to provide a PR to fix this shortly.