[JS1-289] Jetspeed 'takes over' Log4j configuration. ( especially nasty when deploying on jBoss )

• Type: Bug
• Status: Resolved
• Resolution: Incomplete
• Affects Version/s: 1.4b4
• Component/s: Turbine
• Environment: Operating System: Other; Platform: Other
• Bugzilla Id: 19481
• Assignee: Unassigned
• Reporter: Yannick Menager
• Created: 30/Apr/03 21:46
• Updated: 16/Feb/11 21:04
• Resolved: 24/Mar/04 14:36

Description

I've deployed Jetspeed on jboss with the usual tricks ( remove old hsql they
include ). But what is a real pain is that all the Log4j logging gets
redirected to Jetspeed's logfile. I'm assuming that this will affect not just
jboss ( who used log4j by default for all loggging ), but also Tomcat if setup
with log4j in the main classloader ( for sharing logging mechanism to all webapps ).

I've digged through the source code some time ago, and looks like it's Turbine
that's actually causing that mess. However I didn't manage to find a
configuration that would solve the problem.