Hi! Shalin Shekhar Mangar wrote:
Thomas, I don't understand why you say that JDK Logging is only on JVM level. You can have as many different log files as you have Solr instances. All you need to do it to put a logging properties inside Solr's web-inf/classes. For example: # Global Default logging behavior handlers= org.apache.juli.FileHandler, java.util.logging.ConsoleHandler .level=INFO# File Handler specific behavior org.apache.juli.FileHandler.directory = ${catalina.base}/logs org.apache.juli.FileHandler.prefix = myapp1. org.apache.juli.FileHandler.formatter = java.util.logging.SimpleFormatter This will make logging from the webapp goto a log starting with myapp1. You can add these properties to each solr instance you run and you'll get a log file for each instance.
You are right. This is a solution for Tomcat - but no general solution if you run in another container.
Some people have talked about emails and notifications. IMHO, those features don't really belong in a core logging library and are best handled through tools like logcheck ( http://logcheck.org/ ).
Hmmm. This is a matter of taste.
Let's try to enumerate the use-cases that would require Solr to move to a different logging framework and agree on how commonly those use-cases come up. I would like Solr to continue to respect and use the container/JVM's logging configuration without having to make any manual changes.
But what is the cost of going with SL4J? Minor I think. You still would be able to use JUL.
AND: the discussion will be comming to an end... ;-) CU Thomas
