Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 35203 invoked from network); 2 Dec 2002 02:57:40 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Dec 2002 02:57:40 -0000 Received: (qmail 24155 invoked by uid 97); 2 Dec 2002 02:58:37 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 24139 invoked by uid 97); 2 Dec 2002 02:58:36 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 24127 invoked by uid 98); 2 Dec 2002 02:58:36 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Sun, 1 Dec 2002 18:57:20 -0800 (PST) From: "Craig R. McClanahan" To: Tomcat Users List , Subject: Re: "Servlet unavailable" discussion In-Reply-To: <200212011540.41062.pyunusov@rogers.com> Message-ID: <20021201185522.P71634-100000@icarus.apache.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sun, 1 Dec 2002, Paul Yunusov wrote: > Date: Sun, 1 Dec 2002 15:40:41 -0500 > From: Paul Yunusov > Reply-To: Tomcat Users List , > pyunusov@rogers.com > To: Tomcat Users List > Subject: Re: "Servlet unavailable" discussion > > On Sunday 01 December 2002 10:02 am, Paul Yunusov wrote: > > Hello, > > > > I was wondering what, in general, can cause a servlet to be "unavailable" > > as reported by a StandardWrapperValve of Tomcat 4.1.12. > > Thanks, > > Paul > > The invoker servlet discussion was useful but it didn't really address the > question above. (Still, here is a good thread on the invoker servlet: > http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg75346.html) > > There is one answer so far: not reloading a context after changing a class > file in it. Any other observations on causes of "unavailable" servlets? A couple of other ways to get this error (the Tomcat logs will generally include a stack trace of the original exception): * Throw an exception from the init() method of your servlet. (In particular, you can throw an UnavailableException that indicates the servlet is either permanently unavailable or unavailable only for a certain amount of time. * Throw an UnavailableException from the service() (or doGet/doPut) method of your servlet. * Specify a that doesn't exist in your webapp. > Paul Craig -- To unsubscribe, e-mail: For additional commands, e-mail: