Re: Re: Tomcat hangs - Tapestry issue or what?
Thank you guys. Sam, I totally agree with you. Increasing max threads will only delay my worries. My ISP has increased max thread size to 40 so at least I'm unable to reproduce my problem on one or two users. I've tried to get the JConsole to work with SSH but with no luck, seems to be tricky... I'll try more another day. Running JConsole on my local development server works great and I can see clearly that 3 threads is enough for one user. One thread is mysteriously always busy, one thread is in use shortly on every request and if I try hard refreshing I can get another thread running. I'll talk to my nice ISP and see if they can help me running the JConsole. Malin On 12/7/06, Sam Gendler <[EMAIL PROTECTED]> wrote: On 12/7/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > Increase the max thread size on your tomcat context threadpool. It > looks to me like the log message is telling you a max of 10 is > currently allocated for this purpose now. (an abnormally low number) > If this is really only occuring with one or two users on the system, 10 threads should be enough, since no browser will open more than 2 connections to the server at any single instant. It would appear that something is preventing threads from returning to the pool as soon as the request is completed. Bumping the max threads up to a higher number will give you temporary relief, but doesn't fix the underlying problem that is preventing you from reusing threads efficiently. 10 is a very low number, however, and you may well find that bumping the number to 100 will instantly give you enough headroom that you never see the problem again (with reasonable load, anyway). But since this is a hosted server, it is entirely possible you can't bump the maxThreads number. In that case, you can complain to your ISP or else you will have to figure out why the threads aren't being reused. --sam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Tomcat hangs - Tapestry issue or what?
On 12/7/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: Increase the max thread size on your tomcat context threadpool. It looks to me like the log message is telling you a max of 10 is currently allocated for this purpose now. (an abnormally low number) If this is really only occuring with one or two users on the system, 10 threads should be enough, since no browser will open more than 2 connections to the server at any single instant. It would appear that something is preventing threads from returning to the pool as soon as the request is completed. Bumping the max threads up to a higher number will give you temporary relief, but doesn't fix the underlying problem that is preventing you from reusing threads efficiently. 10 is a very low number, however, and you may well find that bumping the number to 100 will instantly give you enough headroom that you never see the problem again (with reasonable load, anyway). But since this is a hosted server, it is entirely possible you can't bump the maxThreads number. In that case, you can complain to your ISP or else you will have to figure out why the threads aren't being reused. --sam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat hangs - Tapestry issue or what?
Increase the max thread size on your tomcat context threadpool. It looks to me like the log message is telling you a max of 10 is currently allocated for this purpose now. (an abnormally low number) On 12/7/06, Malin Ljungh <[EMAIL PROTECTED]> wrote: 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 -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Tomcat hangs - Tapestry issue or what?
if you have ssh access, then you can easily connect Jconsole to your application via an ssh tunnel. Ssh allows you to set up a port on your local machine which will simple transfer every byte received across the ssh connection to any arbitrary port and host on the other side of the connection. don't know anything about Jconsole, but as a generic example, let's pretend Jconsol needs to connect to your server on port 8081. In that case, you would run the following command on your local machine: ssh -L8081:localhost:8081 my.remotehost.com This will cause any connection to port 8081 on your local machine (the first 8081) to be tunneled through the connection to port 8081 on a machine called localhost at the other end of the connection. In this case, that means the machine you are ssh'd into. You could also give a hostname which would be resolved on the server machine, so you can use hostnames that aren't available to the internet itself. Now, you can just tell Jconsole to connect to localhost on port 8081 and all of its traffic will magically cross your ssh tunnel. You can tunnel anything through ssh this way. It is VERY handy when dealing with remote hosts, particularly if you've got a network of machines that are not directly accessible to the internet. Open up ssh on one machine with limited functionality/accessibility and you can then have access to every other machine it can see, including those it shares the 'secured' network with, even if you need more than terminal access. You can even tunnel X across such a connection, allowing you to run gui apps on your remote hosts. A crucial ability when you get an app that requires X in order to run the installer (not as rare as you'd think). This should also work for remote debugging, incidentally. --sam On 12/7/06, Malin Ljungh <[EMAIL PROTECTED]> wrote: Thanks Marcus! The thing is I'm running on hosted environment, I have only an SSH prompt. I'll see if I can reproduce the problem on my local machine and use the Jconsole. For DB access I use Hibernate so I hope it's not leaking db-connections. On 12/7/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat hangs - Tapestry issue or what?
Thanks Marcus! The thing is I'm running on hosted environment, I have only an SSH prompt. I'll see if I can reproduce the problem on my local machine and use the Jconsole. For DB access I use Hibernate so I hope it's not leaking db-connections. On 12/7/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: 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]
RE: Tomcat hangs - Tapestry issue or what?
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]
