Ah I vaguely remember seeing that when we first used logback (on 4.0), as
Shawn says I think its the problem that as logback is starting up, where can
it log before it has configured its logging (catch-22), answer it has to log
to its own internal format.
If memory serves we just disabled that logging, but I don't recall the exact
syntax, I don't have access to my work setup now, but will try and check
tomorrow.
We don't use the request log, so that is one difference.
-----Original Message-----
From: Shawn Heisey
Sent: Tuesday, May 21, 2013 1:42 PM
To: solr-user@lucene.apache.org
Subject: Re: solr UI logging when using logback?
On 5/20/2013 11:23 PM, Boogie Shafer wrote:
in the YYYY_MM_DD-HHmmssSSS.start.log i get messages like this
cat 2013_05_15-141100827.start.log
Establishing start.log on Wed May 15 14:11:12 PDT 2013
14:11:15,756 |-INFO in null - Will use configuration file
[resources/logback-access.xml]
14:11:15,768 |-INFO in
ch.qos.logback.access.joran.action.ConfigurationAction - debug attribute
not set
14:11:15,769 |-INFO in
ch.qos.logback.core.joran.action.StatusListenerAction - Added status
listener of type [ch.qos.logback.core.status.OnConsoleStatusListener]
14:11:15,770 |-INFO in ch.qos.logback.core.joran.action.AppenderAction -
About to instantiate appender of type
[ch.qos.logback.core.rolling.RollingFileAppender]
14:11:15,770 |-INFO in ch.qos.logback.core.joran.action.AppenderAction -
Naming appender as [FILE]
14:11:15,774 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will
use
gz compression
That's really interesting. This appears to be the initialization of
logback itself, not jetty. If nobody steps up who's familiar with
slf4j/logback with jetty, you might need to use a mailing list for one
of those projects.
Thanks,
Shawn
