Hi
The Servlet does not propegate the error. This perticular servlet is one we use
for handling unhandled exceptions and displaying an unexpected-error page to
the user.
_
From web.xml
servlet
servlet-nameexceptionHandler/servlet-name
Imner, Andreas wrote:
...
Hi.
I do not know the answer, but I am sure that if you would like some
answers from the experts on this list, it would not hurt to add some
information like :
- the version of this Tomcat
- where you got it from : is it a standard Tomcat from the Tomcat
website, or
My bad, I did not debug my servlet properly. If had done that earlier I would
have seen that it was the extraction of the exception from the request object
that failed.
When running the webapp in Weblogic as we did earlier, the following code
worked as expected and the exception was properly
My companys web application uses log4j 1.2.8 for logging and have just recently
switched from Weblogic to Tomcat 6.0.18.
Since the we switched to Tomcat, when we do some logging within a servlet
private static final Log log = LogFactory.getLog(ExceptionHandlerServlet.class);
log.error(some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas,
On 6/9/2009 3:31 PM, Imner, Andreas wrote:
My companys web application uses log4j 1.2.8 for logging and have
just recently switched from Weblogic to Tomcat 6.0.18.
Since the we switched to Tomcat, when we do some logging within a
