8273831: PrintServiceLookup spawns 2 threads in the current classloader, getting orphaned #5939
The PrintServiceLookupProvider can spawn 2 threads on WIndows and one thread on Linux. These threads are connected to the classloader of the web application. During undeployment the app classloader gets removed together with the two orphaned threads by the Tomcat.
Looks like the tomcat has special machinery to workaround such threads:
The change updates threads to use the root thread group and null context class loader.
A similar pattern is used here:
@aivanov-jdk please take a look
The text was updated successfully, but these errors were encountered:
@mrserb This change now passes all automated pre-integration checks.
After integration, the commit message for the final commit will be:
At the time when this comment was updated there had been 219 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.
Going to push as commit 6875678.
Your commit was automatically rebased without conflicts.