Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49206

Jenkins Timer threads could get a bogus classLoader

    XMLWordPrintable

Details

    Description

      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. 

      Attachments

        Issue Links

          Activity

            svanoort Sam Van Oort created issue -
            svanoort Sam Van Oort made changes -
            Field Original Value New Value
            Status Open [ 1 ] In Progress [ 3 ]
            jglick Jesse Glick made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            jglick Jesse Glick made changes -
            Remote Link This issue links to "PR 3272 (Web Link)" [ 19966 ]
            jglick Jesse Glick made changes -
            Labels robustness
            svanoort Sam Van Oort made changes -
            Remote Link This issue links to "Core PR #3272 (Web Link)" [ 19967 ]
            svanoort Sam Van Oort made changes -
            Remote Link This issue links to "Core PR #3272 (Web Link)" [ 19967 ]
            oleg_nenashev Oleg Nenashev made changes -
            Resolution Fixed [ 1 ]
            Status In Review [ 10005 ] Resolved [ 5 ]
            bmarwell Ben M made changes -
            Link This issue causes JENKINS-60979 [ JENKINS-60979 ]

            People

              svanoort Sam Van Oort
              svanoort Sam Van Oort
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: