LogSetter in <Context > 2004-01-23 - By Bill Barker
Back
Ok, I don't have access to NetWare, but trying your example on Windows works
fine. The logs are flushed as soon as the error occurs. The only change I
made was to log as well in ClassNotFoundException (so I don't actually have
to set up a database :).
This suggests that the problem is really either with you DB vendor
(unlikely, but I can't rule out that the Driver isn't doing something funky
:), or with your JVM vendor (e.g. Writer.flush isn't really doing what it is
supposed to do).
Also I was testing with the CVS HEAD (aka 3.3.2-dev nightly). The CVS logs
don't show any real changes in the logging code from this and 3.3.1(a),
however. If you are feeling frustrated enough, you could try downloading
the nightly and see if there is any difference :).
"Howard Watson" <howardw@(protected)> wrote in message
news:s00d22f2.021@(protected)
See Attachement
>>> wbarker@(protected) 01/15/04 11:34PM >>>
If you could strip-down your web-app to a minimal version that reproduces
this problem, and post it to BugZilla (or even here, if you don't mind
p**sing off everyone on the list with a big download :), I'd really like to
take a look at it. With a quick eyeballing, I can't see anything in the
code that would produce what you describe.
"Howard Watson" <howardw@(protected)> wrote in message
news:s006834f.078@(protected)
> Thanks for the reply:
>
> I'm using Tomcat3.3.1a for Netware. Took a look at what you talked
> about and had the same problems. But, I did learn a little more about
> the problem. Apparently, I was hacking the context file, deleting log
> files and restarting Tomcat before results were being written.
>
> The problem is not a failure to write to the log, but that it is taking
> about 5 minutes after restarting Tomcat before it will write to the log.
> Then I have exit out of the browser, start a new browser session and
> recreate the error. It then writes everything for that 5 minutes and up
> to the most recent error.
>
> Later, if I generate an error in a new browser session it will write
> that one error, but if I generate multiple errors in a browser session
> (the same error) I have to start a new browser session, recreate the
> error and then it writes all the missing errors including the most
> current one.
>
> Howard
>
> >>> wbarker@(protected) 01/14/04 11:31PM >>>
> Using the CVS HEAD (aka 3.3.2-dev), I have no problems with the
> default
> setup (which defines a <LogSetter> in the 'examples' Context).
>
> "Howard Watson" <howardw@(protected)> wrote in message
> news:s00536d6.043@(protected)
> > Does any know of good document or a tutorial for using LogSetter
> within
> > a Tomcat3.3 <Context>? The log file is created but nothing is written
> to
> > it.
> >
> > I've searched the list and the Internet and find nothing explicit
> about
> > using name= or servletLogger= in <Context><LogSetter /></Context>.
> >
> > If I don't use LogSetter within the <Context>; servlet:inits are
> > written and getServletContext().log("Test ServertLog: ", eSQL);
> writes
> > an error to the <ContextManager> servlet_log correctly.
> >
> > Any ideas?
>
>
>
>
> -- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
> For additional commands, e-mail: tomcat-user-help@(protected)
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---
----
> -- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
> For additional commands, e-mail: tomcat-user-help@(protected)
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)
|
|
