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.
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/ ).
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.
On Wed, Apr 23, 2008 at 12:12 PM, Thomas Peuss <[EMAIL PROTECTED]> wrote:
> Erik Hatcher wrote:
>
> > I'm also opposed (sorry Grant) to tossing in a 3rd party library for
> > logging when the built-in logging facility is sufficient, configurable, and
> > adaptable already.
> >
>
> I must say I never liked JDK logging because it feels like a step back
> when you are used to log4j.
>
> So from my perspective:
> * Solr is a software you mostly run on servers. So log rotation and
> sending emails on errors is a must. Nothing of that is provided by the JDK
> logging implementation (or does not work correctly as someone else has
> stated).
> * JDK logging configuration is only on JVM level. When you use many Solr
> instances in one JVM (we have one per customer) and want several different
> log destinations that is not possible. I want logs per customer - that is
> currently not possible.
>
> I would like to see SL4J based logging in Solr. commons-logging is no
> alternative. It is meant for libraries because "commons-logging does not
> attempt to initialize or terminate the underlying logging implementation
> that is used at runtime; that is the responsibility of the application".
>
> CU
> Thomas
>
--
Regards,
Shalin Shekhar Mangar.
