Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-11161

ThreadDeath occurring under very low load

    XMLWordPrintable

Details

    • Support Request
    • Resolution: Resolved Locally
    • Medium
    • None
    • 3.6.5
    • None
    • None

    Description

      I'm getting a ThreadDeath error after JIRA is up for a few hours. It's just been installed, so usage is very low.

      The error seems to be pointing to quartz perhaps.

      The database on the back end is Oracle 10g RAC, and we're using Active Directory for authentication. Any help would be appreciated!
      ==================================

      2006-09-21 11:58:17,905 WARN [ofbiz.core.entity.SequenceUtil] [SequenceUtil.SequenceBank.fillBank] first select failed: trying to add row, result set was empty for sequence: ChangeGroup
      2006-09-21 11:58:18,028 WARN [ofbiz.core.entity.SequenceUtil] [SequenceUtil.SequenceBank.fillBank] first select failed: trying to add row, result set was empty for sequence: ChangeItem
      Sep 21, 2006 12:09:12 PM org.apache.coyote.http11.Http11Protocol pause
      INFO: Pausing Coyote HTTP/1.1 on http-8080
      Sep 21, 2006 12:09:13 PM org.apache.catalina.core.StandardService stop
      INFO: Stopping service Catalina
      Sep 21, 2006 12:09:13 PM org.apache.catalina.loader.WebappClassLoader findResourceInternal
      INFO: Illegal access: this web application instance has been stopped already. Could not load commons-logging.properties. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
      Sep 21, 2006 12:09:13 PM org.apache.catalina.loader.WebappClassLoader findResourceInternal
      INFO: Illegal access: this web application instance has been stopped already. Could not load META-INF/services/org.apache.commons.logging.LogFactory. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
      Sep 21, 2006 12:09:13 PM org.apache.catalina.loader.WebappClassLoader loadClass
      INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.log4j.Logger. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
      Sep 21, 2006 12:09:13 PM org.apache.catalina.loader.WebappClassLoader loadClass
      INFO: Illegal access: this web application instance has been stopped already. Could not load java.util.logging.Logger. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
      Sep 21, 2006 12:09:13 PM org.apache.catalina.loader.WebappClassLoader loadClass
      INFO: Illegal access: this web application instance has been stopped already. Could not load java.util.logging.Logger. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
      Sep 21, 2006 12:09:13 PM org.apache.catalina.loader.WebappClassLoader loadClass
      INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.commons.logging.impl.SimpleLog. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
      Exception in thread "JiraQuartzScheduler_QuartzSchedulerThread" org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: java.lang.ThreadDeath (Caused by java.lang.ThreadDeath) (Caused by org.apache.commons.logging.LogConfigurationException: java.lang.ThreadDeath (Caused by java.lang.ThreadDeath))
      at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
      at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
      at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
      at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
      at org.quartz.core.QuartzSchedulerThread.getLog(QuartzSchedulerThread.java:446)
      at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:292)
      Caused by: org.apache.commons.logging.LogConfigurationException: java.lang.ThreadDeath (Caused by java.lang.ThreadDeath)
      at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397)
      at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
      ... 5 more
      Caused by: java.lang.ThreadDeath
      at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1221)
      at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1181)
      at org.apache.commons.logging.impl.LogFactoryImpl$1.run(LogFactoryImpl.java:441)
      at java.security.AccessController.doPrivileged(Native Method)
      at org.apache.commons.logging.impl.LogFactoryImpl.loadClass(LogFactoryImpl.java:435)
      at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:376)
      ... 6 more
      Sep 21, 2006 12:09:13 PM org.apache.coyote.http11.Http11Protocol destroy
      INFO: Stopping Coyote HTTP/1.1 on http-8080

      Attachments

        Activity

          People

            Unassigned Unassigned
            648056018c23 Nayan Hajratwala
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: