----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
No sir.
Nothing shows up there either and logging is enabled for both mod_jserv
and JServ. Again, this only appears to be the case on servlets that are
declared in the start up list. Any other servlet which throws an
exception AFTER JServ has completed initialization DOES show up in the
logs.
I haven't looked at the source for this release in any detail, but
barring some really stupid oversight on my part in either
jserv.properties or jserv.conf, this has got me puzzled. And I'm not
new to JServ have used the various 1.x versions for over a year. I
really suspect some fat fingering in my properties/conf setting, but
can't see it. I'm tempted to take the source and rebuild with
JServ.TURBO set to false so that I can maybe get a better grip on what's
going on. But, if anyone can see anything....
Here are my applicable log settings (note that log=true AND
log.channel.servletException=true) - see anything amiss?
jserv.conf
==========
ApJServLogLevel debug
ApJServLogFile /usr/log/httpd/mod_jserv.log
jserv.properties
================
log=true
log.file=/var/log/httpd/jserv.log
log.channel=true
log.channel.info=true
log.channel.servletException=true
log.channel.jservException=true
log.channel.warning=true
log.channel.servletLog=true
log.channel.critical=true
log.channel.debug=false
Fernando Salazar wrote:
>
> ----------------------------------------------------------------
> BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
> WHEN YOU POST, include all relevant version numbers, log files,
> and configuration files. Don't make us guess your problem!!!
> ----------------------------------------------------------------
>
> Does anything end up in the Apache error.log?
>
> - Fernando
>
> > -----Original Message-----
> > Sorry, should have been clearer. I'm trapping for the exception and I'm
> > throwing it, as per:
> >
> > /*
> > Instantiate the singleton PropManager
> > */
> > try
> > {
> > propManager = PropManager.getInstance(config);
> > }
> > catch (Exception e)
> > {
> > log(FRWM + UtilsCommon.convertStackTraceToString(e)); // <---
> > this makes it into the log
> > throw new ServletException(FRWM +
> > UtilsCommon.convertStackTraceToString(e)); // <--- this does not
> > }
> > log(FRWM + PROP_MANAGER_CLASSNAME + CLASS_REFERENCE_OBTAINED);
> >
> >
> > It's not a question of where or why the exception's being thrown - I
> > know precisely the reason. What I can't figure
> > is why ServletExceptions are NOT being logged. I'm guessing I've goofed
> > one of my JServ settings and ServletExceptions are not percolcating
> > backup to JServ. But for the life of me I can't see it....
> >
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
--
Regards,
Marc Connolly
Oracle Corporation
Work: 703.364.2883
Mobile: 703.627.3868
Pager: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
