Rashmi,
You're right. The example you gave throws an exception and it shows
in the localhost log file.
Either Turbine or one of my filters must be trapping the exception. I
was tracing it through with a debugger, but must have missed
something.
Thanks for your help.
WILL
On 3/30/07, Rashmi
On 3/30/07, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
I just concluded a frustrating debugging session in which a servlet
was throwing a ServletException in the init method.
How do you know that the Servlet was throwing an Exception in the init method ?
No error messages
in any log file.
I'm using log4j, but it hasn't been configured at this point. (The
servlet error occurs during configuration).
Still, note that the ServletException is thrown immediately after.
I'd expect Tomcat to pick up uncaught exceptions and stick them in a
log.
WILL
On 3/30/07, Rashmi Rubdi <[EMAIL PROT
It appears that log.fatal is a method in Apache Commons Logging ,
according to the usage
http://carbon.sourceforge.net/modules/core/docs/logging/Usage.html
" FATAL - Severe errors that cause premature termination. Expect these
to be immediately visible on a status console."
According to the abov
Just checked that. It's Jakarta Turbine, incidentally. No, the
servlet catches then rethrows the exception.
catch (Exception e)
{
// save the exception to complain loudly later :-)
initFailure = e;
log.fatal("Turbine: init() fail
On 3/30/07, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
Hi,
I've got a question on logging under Windows (as a service). I'm
running an almost-out-of-the-box install of Tomcat 5.5.20/JRE
1.5.10/Win XP.
I hope the out-of-the-box install configures environment variables such as
JRE_HOME , CATA
Hi,
I've got a question on logging under Windows (as a service). I'm
running an almost-out-of-the-box install of Tomcat 5.5.20/JRE
1.5.10/Win XP.
I just concluded a frustrating debugging session in which a servlet
was throwing a ServletException in the init method. No error messages
in any log
