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

thread named [Jenkins cron thread] but has failed to stop it.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • core
    • None
    • Jenkins 2.381
      tomcat 9.0.70

      I encountered the following errors several times a day.

      09-Dec-2022 12:49:17.493 INFO [Thread-2] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["https-jsse-nio-8443"]
      09-Dec-2022 12:49:17.504 INFO [Thread-2] org.apache.catalina.core.StandardService.stopInternal Stopping service [Catalina]
      09-Dec-2022 12:49:21.426 WARNING [Thread-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jenkins] appears to have started a thread named [Jenkins cron thread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
       java.base@11.0.16.1/java.lang.Object.wait(Native Method)
       java.base@11.0.16.1/java.lang.Object.wait(Object.java:328)
       java.base@11.0.16.1/java.util.TimerThread.mainLoop(Timer.java:527)
       java.base@11.0.16.1/java.util.TimerThread.run(Timer.java:506)
      09-Dec-2022 12:49:21.437 WARNING [Thread-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jenkins] appears to have started a thread named [jenkins.util.Timer [#1]] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
       java.base@11.0.16.1/jdk.internal.misc.Unsafe.park(Native Method)
       java.base@11.0.16.1/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
       java.base@11.0.16.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)
       java.base@11.0.16.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1177)
       java.base@11.0.16.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
       java.base@11.0.16.1/java.lang.Thread.run(Thread.java:834) 09-Dec-2022 12:49:21.447 WARNING [Thread-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jenkins] appears to have started a thread named [jenkins.util.Timer [#2]] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
       java.base@11.0.16.1/jdk.internal.misc.Unsafe.park(Native Method)
       java.base@11.0.16.1/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
       java.base@11.0.16.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)
       java.base@11.0.16.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1177)
       java.base@11.0.16.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
       java.base@11.0.16.1/java.lang.Thread.run(Thread.java:834)
      09-Dec-2022 12:49:21.458 WARNING [Thread-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jenkins] appears to have started a thread named [jenkins.util.Timer [#3]] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
       java.base@11.0.16.1/jdk.internal.misc.Unsafe.park(Native Method)
       java.base@11.0.16.1/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
       java.base@11.0.16.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)
       java.base@11.0.16.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1177)
       java.base@11.0.16.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
       java.base@11.0.16.1/java.lang.Thread.run(Thread.java:834) 09-Dec-2022 12:49:21.467 WARNING [Thread-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jenkins] appears to have started a thread named [AsyncAppender-asyncEventsFileAppender] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
       java.base@11.0.16.1/jdk.internal.misc.Unsafe.park(Native Method)
       java.base@11.0.16.1/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
       java.base@11.0.16.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)
       java.base@11.0.16.1/java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:417)
       org.apache.logging.log4j.core.appender.AsyncAppender$AsyncThread.run(AsyncAppender.java:398)
      09-Dec-2022 12:49:21.477 WARNING [Thread-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jenkins] appears to have started a thread named [AsyncAppender-asyncOctaneFileAppender] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
       java.base@11.0.16.1/jdk.internal.misc.Unsafe.park(Native Method)
       java.base@11.0.16.1/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
       java.base@11.0.16.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)
       java.base@11.0.16.1/java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:417)
       org.apache.logging.log4j.core.appender.AsyncAppender$AsyncThread.run(AsyncAppender.java:398)
      09-Dec-2022 12:49:21.487 WARNING [Thread-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jenkins] appears to have started a thread named [jenkins.util.Timer [#4]] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
       java.base@11.0.16.1/jdk.internal.misc.Unsafe.park(Native Method)
       java.base@11.0.16.1/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
       java.base@11.0.16.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
       java.base@11.0.16.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)
       java.base@11.0.16.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
       java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
       java.base@11.0.16.1/java.lang.Thread.run(Thread.java:834) 09-Dec-2022 12:49:21.646 WARNING [Thread-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [jenkins] appears to have started a thread named [jenkins.util.Timer [#9]] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
       java.base@11.0.16.1/java.lang.Throwable.fillInStackTrace(Native Method)
       java.base@11.0.16.1/java.lang.Throwable.fillInStackTrace(Throwable.java:787)
       java.base@11.0.16.1/java.lang.Throwable.<init>(Throwable.java:255)
       org.slf4j.jul.JDK14LoggerAdapter.fillCallerData(JDK14LoggerAdapter.java:182)
       org.slf4j.jul.JDK14LoggerAdapter.innerNormalizedLoggingCallHandler(JDK14LoggerAdapter.java:155)
       org.slf4j.jul.JDK14LoggerAdapter.log(JDK14LoggerAdapter.java:172)
       org.slf4j.bridge.SLF4JBridgeHandler.callLocationAwareLogger(SLF4JBridgeHandler.java:221)
       org.slf4j.bridge.SLF4JBridgeHandler.publish(SLF4JBridgeHandler.java:303)
       java.logging@11.0.16.1/java.util.logging.Logger.log(Logger.java:979)
       org.slf4j.jul.JDK14LoggerAdapter.innerNormalizedLoggingCallHandler(JDK14LoggerAdapter.java:156)
       org.slf4j.jul.JDK14LoggerAdapter.log(JDK14LoggerAdapter.java:172)
       org.slf4j.bridge.SLF4JBridgeHandler.callLocationAwareLogger(SLF4JBridgeHandler.java:221)
       org.slf4j.bridge.SLF4JBridgeHandler.publish(SLF4JBridgeHandler.java:303)
       java.logging@11.0.16.1/java.util.logging.Logger.log(Logger.java:979)
       org.slf4j.jul.JDK14LoggerAdapter.innerNormalizedLoggingCallHandler(JDK14LoggerAdapter.java:156)
       org.slf4j.jul.JDK14LoggerAdapter.log(JDK14LoggerAdapter.java:172)
       org.slf4j.bridge.SLF4JBridgeHandler.callLocationAwareLogger(SLF4JBridgeHandler.java:221)
       org.slf4j.bridge.SLF4JBridgeHandler.publish(SLF4JBridgeHandler.java:303)
       java.logging@11.0.16.1/java.util.logging.Logger.log(Logger.java:979)
       org.slf4j.jul.JDK14LoggerAdapter.innerNormalizedLoggingCallHandler(JDK14LoggerAdapter.java:156)
       org.slf4j.jul.JDK14LoggerAdapter.log(JDK14LoggerAdapter.java:172)
       org.slf4j.bridge.SLF4JBridgeHandler.callLocationAwareLogger(SLF4JBridgeHandler.java:221)
       

            Unassigned Unassigned
            aa673 Linxiang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: