I've deployed Jahia in Jboss, and when I start it, I've got the message "Invalid Console appender, log4j is looping..."

I've tried to delete the jahia's log4j file, and to add some reference n the jboss'one, but no matters...

Here is my log4j file configuration


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

<!-- ===================================================================== -->
<!-- -->
<!-- Log4j Configuration -->
<!-- -->
<!-- ===================================================================== -->






<appender-ref ref="CLUSTER"/>



<appender-ref ref="CLUSTER"/>

-->








-->

<!-- ============================== -->
<!-- Append messages to the console -->
<!-- ============================== -->









<!-- The default pattern: Date Priority [Category] Message\n -->













<!-- ====================== -->
<!-- More Appender examples -->
<!-- ====================== -->

<!-- Buffer events and log them asynchronously


<appender-ref ref="FILE"/>
<appender-ref ref="CONSOLE"/>
<appender-ref ref="SMTP"/>

-->

<!-- EMail events to an administrator












-->

<!-- Syslog events






-->

<!-- Log events to JMS (requires a topic to be created)






-->

<!-- Log events through SNMP


















-->

<!-- ================ -->
<!-- Limit categories -->
<!-- ================ -->

<!-- Limit the org.apache.commons category to INFO as its DEBUG is verbose -->




<!-- Limit JBoss categories to INFO -->




<!-- Decrease the priority threshold for the org.jboss.varia category



-->

<!-- Show the evolution of the DataSource pool in the logs [inUse/Available/Max]



-->

<!--
| An example of enabling the custom TRACE level priority that is used
| by the JBoss internals to diagnose low level details. This example
| turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
| subpackages. This will produce A LOT of logging output.






-->

<!--
| Logs these events to SNMP:
- server starts/stops
- cluster evolution (node death/startup)
- When an EJB archive is deployed (and associated verified messages)
- When an EAR archive is deployed



<appender-ref ref="TRAP_LOG"/>




<appender-ref ref="TRAP_LOG"/>




<appender-ref ref="TRAP_LOG"/>




<appender-ref ref="TRAP_LOG"/>




<appender-ref ref="TRAP_LOG"/>



-->




























<!-- ======================= -->
<!-- Setup the Root category -->
<!-- ======================= -->



<appender-ref ref="CONSOLE"/>
<appender-ref ref="FILE"/>
<appender-ref ref="STDOUT"/>


<!-- Clustering logging -->
<!-- Uncomment the following to redirect the org.jgroups and
org.jboss.ha categories to a cluster.log file.














<appender-ref ref="CLUSTER"/>



<appender-ref ref="CLUSTER"/>

-->

</log4j:configuration>

In bold are the configuration from Jahia.

Is the problem coming from the different webapps of Jahia which include log4j files.....???

tks in advance
Matt