Hi,
Thanks again for the reply. I can't reproduce the END event so probably
I was mistaken, sorry about that. It is indeed the ERROR/TIMEOUT event.
If an exception occurs during the handling of this event (an unforseen
runtime exception for example), then tomcat calls the event method again
with the ERROR/TIMEOUT event, ad infinitum (or at least lots of times ;-))
Regards,
Sebastiaan
Rémy Maucherat wrote:
On 4/2/07, Rémy Maucherat <[EMAIL PROTECTED]> wrote:
> I was also just discovered that in the 6.0.10 version that an
exception
> in the END event causes the END event to called again; this means that
> an uncaught RuntimeException could potentially cause Tomcat to go
into a
> loop of an infinite number of END events.
I will verify that.
I have looked at it, and I don't understand the issue. First of all,
END is a theorical event, which cannot really be called at the moment,
except in very specific cases (when the connector is stopped). Can you
give more details ? Maybe you meant ERROR ?
Rémy
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
