Slippery slope here, Chainsaw is now starting up with no errors using log4j1.2, but when I try to load a configuration file I've been using ok prior, I get this output, and nothing appears to happen (see below).

Obviously the DOMConfigurator in 1.2 knows nothing about plugins. I wonder if we're going to constantly run into these sorts of problems. Are we pushing the proverbial up hill here? Should we leave Chainsaw reliance on 1.3, and move on to working on 2.0?

log4j:WARN Continuable parsing error 3 and column 82
log4j:WARN Element type "log4j:configuration" must be declared.
log4j:WARN Continuable parsing error 4 and column 73
log4j:WARN Element type "plugin" must be declared.
log4j:WARN Continuable parsing error 5 and column 40
log4j:WARN Element type "param" must be declared.
log4j:WARN Continuable parsing error 6 and column 46
log4j:WARN Element type "param" must be declared.
log4j:WARN Continuable parsing error 8 and column 75
log4j:WARN Element type "plugin" must be declared.
log4j:WARN Continuable parsing error 9 and column 46
log4j:WARN Element type "param" must be declared.
log4j:WARN Continuable parsing error 10 and column 40
log4j:WARN Element type "param" must be declared.
log4j:WARN Continuable parsing error 12 and column 10
log4j:WARN Element type "root" must be declared.
log4j:WARN Continuable parsing error 13 and column 29
log4j:WARN Element type "level" must be declared.


The XML configuration file is (I'm ssh tunneling in this case):

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration >
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/"; debug="true"> <plugin name="qaapp1" class="org.apache.log4j.net.SocketHubReceiver">
      <param name="Port" value="4560"/>
      <param name="Host" value="127.0.0.1" />
   </plugin>
<plugin name="qa index" class="org.apache.log4j.net.SocketHubReceiver">
      <param name="Host" value="127.0.0.1" />
      <param name="Port" value="4561"/>
   </plugin>
   <root>
      <level value="debug"/>
   </root>
</log4j:configuration>

Reply via email to