First, which tomcat ? For 3.3:
> 1) Where is logging done? Could you give me pointers to specific > classes/methods I need to modify? The interface is o.a.t.util.log, o.a.t.modules.config.LogSetter will plug the default implementation. Write a new implementation and replace LogSetter, and you can plug your own logger. > 2) Performance - is declaring SQL INSERTs as DELAYED or LOW_PRIORITY enough? > Or making static per-db-url buffering and writing many (16-64?) records at > once? The 'default' logger is using a queue and does some buffering, you may want to cut&paste. Log4j can do that also - so it may be better to just use log4j. > 3) Is it possible to rewrite Tomcat's logging to enable pluggable logging > engines? (Standard or Log4j) It should be. Creating a log4j logger module is very high on my todo list, now that Ceki added the posiblity to have separated loggers per webapp and plug a controler. If you want to help ( or just do the whole thing ) - I would be happy to help. > 4) I saw suggestion to move to JDK 1.4 logging - _please_ if/when you decide > to change logging, move to Log4j instead of this. I don't think we'll change the logging ( at least in 3.3 ), but provide additional logging modules - and people can choose whatever is best for their project. Log4j is my favorite ( since it's apache and used by so many people) , I am also interested in a jdk1.4 logging module - but any other logger should work fine and is welcomed. Costin
