[jboss-jira] [JBoss JIRA] Updated: (JBAS-3199) Tomcat consuming 99, 9% CPU
Dimitris Andreadis (JIRA)
jira-events at jboss.com
Mon Jul 24 13:51:11 EDT 2006
[ http://jira.jboss.com/jira/browse/JBAS-3199?page=all ]
Dimitris Andreadis updated JBAS-3199:
-------------------------------------
Fix Version/s: (was: JBossAS-4.0.5.CR1)
Priority: Major (was: Minor)
> Tomcat consuming 99,9% CPU
> --------------------------
>
> Key: JBAS-3199
> URL: http://jira.jboss.com/jira/browse/JBAS-3199
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: SUSE LINUX 10.0 (X86-64)
> VERSION = 10.0
> java version "1.5.0_03"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_03-b07)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_03-b07, mixed mode)
> Reporter: Petri Rautakoski
> Assigned To: Remy Maucherat
>
> Suddenly Tomcat reserves all CPU resources. When investigated from web-console we get statcktrace for thread consuming CPU:
> Thread: http-0.0.0.0-6060-46 : priority:5, demon:true, threadId:1155, threadState:RUNNABLE, threadLockName:null
> java.lang.StrictMath.floor(Native Method)
> java.lang.Math.floor(Math.java:407)
> org.apache.naming.resources.ResourceCache.allocate(ResourceCache.java:233)
> org.apache.naming.resources.ProxyDirContext.cacheLoad(ProxyDirContext.java:1599)
> org.apache.naming.resources.ProxyDirContext.cacheLookup(ProxyDirContext.java:1448)
> org.apache.naming.resources.ProxyDirContext.lookupCache(ProxyDirContext.java:1376)
> org.apache.catalina.servlets.DefaultServlet.renderHtml(DefaultServlet.java:1314)
> org.apache.catalina.servlets.DefaultServlet.render(DefaultServlet.java:1102)
> org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:807)
> org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:335)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
> org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
> java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list