Re: Marking servlet ... as unavailable

2007-05-19 Thread Philipp Führer - netzbeben
Hi Joe, the problem is, that the UnavailableException is buggy in some tomcat versions. If thrown, tomcat will set the servlet as unavailable but won't print the exception message. Use the newest tomcat-version. Or change all UnavailableException to ServletException, so you will see the exception

Re: Marking servlet [] as unavailable, again...

2007-03-26 Thread Simon Brooke
On Sunday 25 March 2007 02:44, Martin Gainty wrote: > Simon- > > something is happening to interfere with the successful completion of > init() method of your Servlet such as cannot find classes such as > 'uk.co.weft.exceptionhandler.BugzillaExceptionHandler' > or one of the init-param in web.xml c

Re: Marking servlet [] as unavailable, again...

2007-03-24 Thread Martin Gainty
s n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. - Original Message - From: "Simon Brooke" <[EMAIL PROTECTED]> To: Sent: Saturday, March 24, 2007 11:28 AM S

Marking servlet [] as unavailable, again...

2007-03-24 Thread Simon Brooke
Yes, I've read through previous threads on this subject; I haven't found anything which helps me. Recently I've had a spate of unexplained 'Marking servlet [] as unavailable' issues on my development server. It is a development server, and so, of course, all the servl

Re: Marking servlet ... as unavailable

2007-03-05 Thread Joe Siebenmann
I could be wrong, but it appeared that when the Servlet was flagged as unavailable, that THAT would cause a series of other problems which the stackTrace() showed, not what actually caused it to be flagged as unavailable. If you're right, that it was flagged outside of Tomcat, than there isn't a

Re: Marking servlet ... as unavailable

2007-03-05 Thread David Delbecq
En l'instant précis du 04/03/07 22:27, Joe Siebenmann s'exprimait en ces termes: > > It would be nice if there was some better information available > as to what it "didn't like" for it to flag it as "unavailable". > Nothing of any value was in any of the log files. > You logs stated: SEVERE: A

RE: Marking servlet ... as unavailable

2007-03-04 Thread Joe Siebenmann
oe Siebenmann --- On Sun 03/04, Joe Siebenmann < [EMAIL PROTECTED] > wrote: From: Joe Siebenmann [mailto: [EMAIL PROTECTED] To: users@tomcat.apache.org Date: Sun, 4 Mar 2007 09:58:49 -0500 (EST) Subject: Marking servlet ... as unavailable Hi All,I've hit this problem and my develop

Marking servlet ... as unavailable

2007-03-04 Thread Joe Siebenmann
Hi All, I've hit this problem and my development has come to a screeching halt. :-\ I'm using Tomcat 5.5.17 with a JDK/JRE of 1.5.0_11 on a Windows XP Pro SP2 system. In my Servlets I use: RequestDispatcher dispatcher = getServletContext().getRequestDispatcher("/servlet/BlahServlet"); if (