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 >>> [EMAIL 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" <[EMAIL PROTECTED]> wrote in message news:[EMAIL 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
