Hello Benjamin, This sounds like an infinite loop - a bug in your application. This can happen if you don't use synchronization properly, for example write and read to/from Hashmap without synchronization from 2 parallel threads. When you detect this behaviour again, create a full thread dump by sending QUIT signal to the process: kill -QUIT pid tomcat will print out the thread dump into catalina.out. Look for suspicious threads or just send it to the list again.
Btw, which tomcat version do you use exactly? regards Leon On Wed, Jul 29, 2009 at 10:58 AM, <b.henr...@pepperone.be> wrote: > Hello, > > > > We have sometimes Tomcat (5.x) who consume all the CPU (or 50 %) of the > CPU constantly in our productions servers (Linux or Windows). > > Our applications aren't doing anything and the only solution is to > restart Tomcat. > > I don't know if the problem is related to Tomcat or to the JVM (Sun) but > I suspect that can occur when all the physical memory of the server is > used. > > However, we set heap (between 1GO and 2GO) like this: Xmx = Xms < > [physical memory available] when the server starts, so Tomcat shouldn't > have disk swapping problem. (Am I wrong?) But other services can eat the > memory and the server can begin to swap... > > Does anyone has had a problem like this? > > Thank you. > > > > Benjamin > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org