Thanks for your response Rémy, it is much appreciated.
I have followed that guide step by step and another guide in "Pro
Jakarta Tomcat 5" Which contains details of tomcat 5.5 as well.
So far, all I get in the tomcat.log with the configuration specified in
that link is masses of debug with no det
On 2/23/07, Tom Crinson <[EMAIL PROTECTED]> wrote:
The only way I have found to get round this problem is to define my own
Struts Request processor and override processException, and log the
uncaught exceptions in there to a logger specified in the webapp
log4j.properties.
So, my question is, i
Hi,
I have recently upgraded to tomcat 5.5.17 (on red hat linux on java 5)
and have noticed and read about the disappearance of the
element in the context which used to log stack traces and uncaught
exceptions.
I have looked through this list and although there are one or two
threads on it I c
