The LogFactor5 UI is launched inside the server VM, and consumes a lot of memory. It also causes problems with redeployment of applications. You can't use it if you want the log UI on another computer than the server.
Chainsaw runs in a separate VM and therefore uses sockets to transmit the log messages to the console.
We decided to switch to Chainsaw for the reasons above. Of course you can still use LF5 if you prefer that UI, and can live with the occasional out of memory exceptions.
Regards, Julien
Scott McMullan wrote:
Hmmm..., why are we on a wild goose chase trying to get Chainsaw working with OXF when you have already integrated with the Logfactor5 gui log reader? All I had to do was uncomment out the following line in my log4j.xml file:
<!-- This is a graphical log analyser --> <appender name="LF5Appender" class="org.orbeon.oxf.util.LF5Appender"> <param name="MaxNumberOfRecords" value="1000"/> </appender>
I'm curious, what was the advantage sending us down the Chainsaw path?
-Scott
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
