It works most of the time but sometimes it doesn't for no discernible reason.
:( One of life's great mysteries that I am looking in to.
In Response To:
Hi Chris,
I guess you're question pointed to Sam, right?
Anyways, that's also what I think.
According to the specs a *noncaught* exception
Hi Chris,
I guess you're question pointed to Sam, right?
Anyways, that's also what I think.
According to the specs a *noncaught* exception should trigger the errorpage
At least here it's working as expected ;)
Cheers
Gregor
--
what's puzzlin' you, is the nature of my game
gpgp-fp: 79A84FA526
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gregor,
[EMAIL PROTECTED] wrote:
> however, sometimes for errors (like trying to access
> a null object) the page is not invoked but there's a stack trace in
> the logs.
Is it possible that the exception is being caught and logged before it
can fall
That's exactly what I have done. I have even tested it by having a servlet do a
int i = 500/0; which causes a 500 error and a divide by zero exception which
invokes the page correctly with the error and the stack trace; however,
sometimes for errors (like trying to access a null object) the page
try to put something like this into your web.xml (i hope that is what
you've been asking for):
java.lang.Throwable
/errorPages/generalError.html
That page should just display some message like "general error
occured, please report to webmaster... ". The error itself you then
sho
I have configured a servlet to display an error message and a stack trace for
500 errors 9defined in web.xml). It works sometimes and not at others? By this
i mean some 500 errors are caught and reported the others just cause an error
and failure.
In Response To:
Does anybody have an example
