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
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
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 could be incorrectly spelled or not there
put in log.debug or S
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
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
Hi All,
I was at least able to get the Servlet that was "unavailable"
to finally show up. This has been one of the most frustrating
things I've come across.. :-\
I figured that something was happening in the Servlet before
the Servlet that was being flagged as "unavailable", so I
commented out
