https://issues.apache.org/bugzilla/show_bug.cgi?id=48860

           Summary: High CPU usage
           Product: Tomcat 6
           Version: 6.0.24
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Connectors
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: chris....@ordosinc.com


I upgrade from tomcat 4 to tomcat 6. After upgrade, I receive the following
errors. I created a simple foo.jsp with <%= "Hello" %>
When start the tomcat6, the CPU usage is 0%. When I open the foo.jsp, the CPU
instantly jump to 100% and stays forever. I using mysql jdbc connector J
connecting to mysql database. Please advise. Thanks.

Mar 4, 2010 4:23:31 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Timer-0] but
has failed to stop it. This is very likely to create a memory leak.
M
Mar 4, 2010 4:24:38 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-4] but
has failed to stop it. This is very likely to create a memory leak.
Mar 4, 2010 4:24:38 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Timer-0] but
has failed to stop it. This is very likely to create a memory leak.
Mar 4, 2010 4:24:38 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-8] but
has failed to stop it. This is very likely to create a memory leak.
M

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to