If you have "stuck servlets" (which I take to mean you've got bugs in your app that causes your servlets to stop responding), how would calling those exact same servlets through Apache be any different? If the problem is really the servlet, it's going to cause "runaway threads" (without a concise description of what you are really seeing, I don't really know what you mean by this) either way. The only answer is to correct the bugs in your app that are causing the servlet not to complete its responses.
Regarding restarting a webapp without restarting Tomcat, you should read up on the Manager servlet that comes with Tomcat 4.0 and 4.1: http://jakarta.apache.org/tomcat/tomcat-4.0-doc/manager-howto.html http://jakarta.apache.org/tomcat/tomcat-4.1-doc/manager-howto.html You should also upgrade to 4.0.5 or 4.1.12 to pick up the most recent bugfixes (and the fix for the recent security vulnerability that was reported against Tomcat versions 4.0.4 (and below) and 4.1.11 (and below). Craig On Mon, 30 Sep 2002, Oskar Bartenstein wrote: > Date: Mon, 30 Sep 2002 12:30:40 +0900 > From: Oskar Bartenstein <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > To: Tomcat Users List <[EMAIL PROTECTED]> > Subject: Re: Best Practices Question > > Sun, 29 Sep 2002 18:39:54 -0700 (PDT) "Craig R. McClanahan" <[EMAIL PROTECTED]> >said: > > IMHO, anyone who goes to all the extra effort of configuring > > Apache+Tomcat, instead of Tomcat alone, is nuts unless they need it. > > Valid reasons to need it include: > > I am pondering one more: reducing interruption of service. > > Tomcat can handle many webapps with ease, and you can > allow as many threads as you need to serve your users. > > But when a single servlet gets stuck, you have to restart the > whole Tomcat machinery, taking down all running webapps, possibly > loosing session data and certainly interrupting service to all users, > including those completely unrelated to the hanging servlet. > My experience is based on Tomcat 4.0.3 and 3.x only. > I searched quite a while but failed to find a way to > monitor and catch individual runaway servlet threads. > Please correct me if I am wrong. > > In that respect, with due appreciation for this great work, I think > standalone Tomcat does not scale well. > > To avoid this, Apache just working as a proxy on port 80 for > many independent instances of Tomcat on their own ports > seems a feasible solution. > >>From experience, I dislike the idea of going back to Apache+Tomcat. > Both are fine by themselves, but the combi is a hassle. > > Any hints for better alternatives to reduce the impact of stuck servlets? > > -- > Dr. Oskar Bartenstein [EMAIL PROTECTED] > IF Computer Japan http://www.ifcomputer.com > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
