-
Bug
-
Resolution: Fixed
-
Minor
The Timer threads are lazily created by its executorService, so if an invocation to the Timer threads is made in a Thread context with a different contextClassloader than the default, the Timer thread will receive this contextClassloader.
Noted when fixing an analogous error in the Pipeline Timeout utility https://github.com/jenkinsci/workflow-support-plugin/pull/53 jglick – that error caused a Groovy memory leak.
- causes
-
JENKINS-60979 Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
-
- Closed
-
- links to
Code changed in jenkins
User: Sam Van Oort
Path:
core/src/main/java/hudson/util/ClassLoaderSanityThreadFactory.java
core/src/main/java/jenkins/util/Timer.java
core/src/test/java/jenkins/util/TimerTest.java
http://jenkins-ci.org/commit/jenkins/2a6fc653ee7b13adde18515b21f7e6dc1200fa8a
Log:
Fix
JENKINS-49206by ensuring Timer threads get standard classloader (#3272)JENKINS-49206by ensuring Timer threads get standard classloader