Logging in the example solr+jetty setup

Hi There,

I'm new to solr, and so far I've been impressed. One thing
I'm curious
about, as a newbie, is the source of some of the log
messages that
show up in the example solr+jetty setup, found in the 1.2
distribution's example directory.

I'm seeing two kinds of log messages. First there are ones
of this sort:

Sep 23, 2007 1:20:06 AM
org.apache.solr.handler.XmlUpdateRequestHandler update
Sep 23, 2007 1:20:06 AM org.apache.solr.core.SolrCore
execute
Sep 23, 2007 1:20:06 AM
org.apache.solr.update.DirectUpdateHandler2 commit

which seem to be debugging info about which methods in the
solr code
are being invoked. Then there are ones of this sort

INFO: added id= in 77ms
INFO: /update  0 82
INFO: start
commit(optimize=false,waitFlush=false,waitSearcher=true)

which provide a more user-oriented, action-centric (vs
code-centric)
perspective.

The latter messages, I see, are generated in the solr code,
in calls
to log.info(), log.severe(), etc.. But where are the
code-oriented,
method invocation messages being generated? Perhaps the solr
code is
generating these as well, though I haven't found code for it
yet. Is
this perhaps something that jetty is doing? Does the example
jetty
setup somehow ask the java VM to automatically log certain
method
calls?

Thanks,
Chris

Okay, I figured it out. The method invocation messages are
being
generated by the java logging api. The default logging
handler in the
solr+jetty setup is java.util.logging.ConsoleHandler. That
handler (or
perhaps java.util.logging.SimpleFormatter, its default
formatter)
causes a what-method-am-I-in message to be printed to the
console
immediately before printing the message actually passed to
log.info(),
log.warning(), or whatever.

On 9/23/07, Chris Harris <ryguasugmail.com> wrote:
> Hi There,
>
> I'm new to solr, and so far I've been impressed. One
thing I'm curious
> about, as a newbie, is the source of some of the log
messages that
> show up in the example solr+jetty setup, found in the
1.2
> distribution's example directory.
>
> I'm seeing two kinds of log messages. First there are
ones of this sort:
>
> Sep 23, 2007 1:20:06 AM
org.apache.solr.handler.XmlUpdateRequestHandler update
> Sep 23, 2007 1:20:06 AM org.apache.solr.core.SolrCore
execute
> Sep 23, 2007 1:20:06 AM
org.apache.solr.update.DirectUpdateHandler2 commit
>
> which seem to be debugging info about which methods in
the solr code
> are being invoked. Then there are ones of this sort
>
> INFO: added id= in 77ms
> INFO: /update  0 82
> INFO: start
commit(optimize=false,waitFlush=false,waitSearcher=true)
>
> which provide a more user-oriented, action-centric (vs
code-centric)
> perspective.
>
> The latter messages, I see, are generated in the solr
code, in calls
> to log.info(), log.severe(), etc.. But where are the
code-oriented,
> method invocation messages being generated? Perhaps the
solr code is
> generating these as well, though I haven't found code
for it yet. Is
> this perhaps something that jetty is doing? Does the
example jetty
> setup somehow ask the java VM to automatically log
certain method
> calls?
>
> Thanks,
> Chris
>