tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Smith" <sat-g...@home.com>
Subject Re: More Tomcat problems.
Date Tue, 03 Oct 2000 17:34:35 GMT
Endre,

Tomcat isn't "crashing", it's doing what it is supposed to,
namely passing an exception on up the handler chain.
Other servlets and JSP continue to operate normally.
This is the opposite of "crashing." Scalability depends
on reliable exception handling.

The point of my post was to suggest Panagiotis try
debugging his base code before putting it into the servlet
runner, then blaiming tomcat/apache for "not reporting
the error" when his code fails. The servlet runner itself
is actually pretty stable, not to talk about apache, which
is rock solid.

Regards,

Dave
----- Original Message -----
From: "Endre StĂžlsvik" <Endre@Stolsvik.com>
To: <tomcat-user@jakarta.apache.org>
Sent: Sunday, December 03, 2000 1:02 PM
Subject: Re: More Tomcat problems.


> On Mon, 2 Oct 2000, Dave Smith wrote:
>
> | More Tomcat problems.Panagiotis,
> |
> | Are you using a try block around the code to catch SQLExceptions
> | in your development setup?
> |
> | This is what is happening: you are throwing an exception without
> | a handler. The jvm just unwinds to the top and drops you out.
>
> I'm just curious; isn't this strange behaviour? Could a "bad" servlet
> crash Tomcat totally, then? I'm thinking of virtual servers, several
> domains sharing a Tomcat.
>
>
> --
> Mvh,
> Endre
>


Mime
View raw message