[Helma-user] log4j

[Michael Platzer]

hi,

today i played around with the log4j-configuration, and i am really 
tempted to switch to log4j (development- as well as production-setups) 
for the following reasons:
* the SMTP-Appender (-> get emails for FATAL messages)
* the JDBC-Appender (-> store ERROR messages persistently in a database; 
that way they are safely stored, and wont get lost when deleting log-files)
* Chainsaw (-> integrate a java-applet into web-manage-interface and 
watch real-time server-logs remotely over the web)
* asynchronous logging: could be a performance improvement, especially 
when doing extensive logging for high-traffic websites;
* we can start using different log-levels within our applications

well, but i want to achieve a log4j-setup that is at least as powerful 
as the default helma logging mechanism. but i don't know how to solve 
the following issues:
* If I start a new application in helma, then the default helma logger 
automatically creates the according log-files. With log4j I would need 
to add an extra file-appender to (a global) log4j.xml to start distinct 
log-files.
* With the default helma logger I can switch the log-level during 
runtime by changing "debug" in app.properties. How can I tell Helma that 
log4j.xml has been updated? (the same is true for logSQL=true)
* I would like to use distinct log4j.xml files for each application, and 
not have to share one global log4j.xml for the whole Helma installation. 
Possible?
* As far as I know gzipped logfiles are not possible within log4j 1.2.*, 
but are an upcoming feature for 1.3.* This is not such a big issue, 
since I could use a DailyRollingFileAppender in the meantime, and let 
unix-logrotate do the gzipping.

maybe someone has hints/solutions for these issues. i would love to 
switch to log4j, but am a bit worried about the extra maintenance-burden 
when dealing with lots of apps running under a single helma-installation.

out of curiosity: who is using log4j (for development, resp for 
production)? and how does your setup look like?
i attached my current log4j.xml to this email.

regards,
  michi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: log4j.xml
Type: text/xml
Size: 2710 bytes
Desc: not available
Url : http://helma.org/pipermail/helma-user/attachments/20060814/8b37a366/attachment.xml