It turns out that by copying log4j into server/lib we seem to be switching Tomcat from using JSR-47 logging to log4j logging. Normally this would raise a warning saying that log4j was not configured. However, the ws-commons/policy file contains a minimal log4j.properties file which provides log4j configuration; unfortuately the configuration is such that most Tomcat messages (and hence Tuscany ones) do not get logged.
I changed the scripts to no longer copy log4j and now we get the log messages we expect. -- Jeremy Jeremy Boynes wrote: > [EMAIL PROTECTED] wrote: > >>Author: jboynes >>Date: Tue Apr 4 15:47:29 2006 >>New Revision: 391434 >> >>URL: http://svn.apache.org/viewcvs?rev=391434&view=rev >>Log: >>error logging for Tomcat listener >> > > > The first time I ran testing/tomcat after this change I got a Error from > the runtime; this did show up on the console (attached as err1.txt). > This seems to be because the Error propogates up and is output by Tomcat. > > I did a clean to fix that which made the errors go away. I recompiled to > add in an explicit problem but did not get any error logged. The > log.error() statements are being executed but nothing is showing up in > Tomcat. > > I think we need to do a little more digging to find out why nothing is > output when log.error() is called. > > -- > Jeremy
