If you're running on Java 5, fire up Jconsole and have a look at Threads Tab. It'll tell you where your threads are hanging. A common problem is leaking pooled Db-connections - but that's only a guess.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Malin Ljungh > Sent: Thursday, December 07, 2006 9:20 AM > To: Tapestry users > Subject: Tomcat hangs - Tapestry issue or what? > > Hi all! > > I have prolem with my Tomcat hangs (sometimes). I can see the > following in my logs: > > Dec 6, 2006 4:43:13 PM > org.apache.tomcat.util.threads.ThreadPool logFull > SEVERE: All threads (10) are currently busy, waiting. > Increase maxThreads > (10) or check the servlet status > > But it occurres even on very low load (one or two users) so I > assume it's something wrong here... requests not ending > correctly or something. When it works it works very rapidly > so it shouldn't be what I do in the request that is the issue. > > I really don't believe it's a Tapestry issure but I thought > I'd ask here anyway.. Maybe someone has experienced the same problem? > > Anyone? > > /Malin > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
