Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-8970

Memory leak errors when trying to shut down Tomcat

    Details

    • Type: Bug Fix Bug Fix
    • Status: Open Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development, Performance
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-6585Look into possible memory and thread local leaks reported by tomcat on a shutdown
      KULRICE-4959On shutdown, KS' Rice outputs messages that may indicate Quartz isn't shutting down correctly
      KULRICE-3342Verify that Rice shuts down cleanly when requested to
      KULRICE-6435Make it so that Rice 2.0 can shut down cleanly
      KULRICE-7316ReloadingDataDictionary (when configured) prevents Rice from shutting down cleanly
      KULRICE-4957Update surefire plugin due to memory leak
      KULRICE-1736can't shut down the ksb
      KULRICE-13408Very large HistoryFlows cause Out Of Memory error.
      KULRICE-8770easyXDM issues with Firefox and Tomcat
      KULRICE-4990fixing log4j errors in rice on tomcat startup
    • Rice Module:
      Rice Core
    • Application Requirement:
      KC
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      We see the following errors when we shutdown tomcat. Following is the stack trace. KULRICE-6585 seems to have addressed most of these issues but the following still seem to appear.

      SEVERE: The web application [/coeus] appears to have started a thread named [JotmBatch] but has failed to stop it. This is very likely to create a memory leak.
      Feb 4, 2013 1:27:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: The web application [/coeus] appears to have started a thread named [JotmClock] but has failed to stop it. This is very likely to create a memory leak.
      Feb 4, 2013 1:27:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: The web application [/coeus] appears to have started a thread named [rice.ksb.scheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.
      

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Gayathri Athreya
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Structure Helper Panel