[ http://issues.apache.org/jira/browse/TUSCANY-149?page=all ]
Jeremy Boynes closed TUSCANY-149:
---------------------------------
Resolution: Fixed
Assign To: Jeremy Boynes
The test setup was copying log4j into server/lib causing Tomcat (through its
use of clogging) to switch from JSR-47 to log4j logging.
Unfortunately, the ws-commons/policy jar contains a minimal log4j.properties
file which configured log4j in a way that resulted in the suppression of most
messages.
I changed the configuration script so that it no longer installs log4j as part
of test setup. I also updated the wiki to remove log4j from the list of jars to
be installed.
> Messages logged by Tomcat integration don't appear in log files
> ---------------------------------------------------------------
>
> Key: TUSCANY-149
> URL: http://issues.apache.org/jira/browse/TUSCANY-149
> Project: Tuscany
> Type: Bug
> Components: Java SCA Tomcat Integration
> Reporter: Jeremy Boynes
> Assignee: Jeremy Boynes
> Priority: Blocker
>
> Messages (informational or error) logged by the Tomcat integration code do
> not get output to the screen or to the log files.
> Call to log.info() or getLogger().error() are being made but the logging
> implementation decides that the log level is not enabled.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
