It is possible. Also, those settings are not saved across restarts. You really should use a logging properties file.
Other ways to check on freezes: 1) run garbage collection logging or monitoring. 2) poll the statistics requesthandler and log. 3) poll the thread list and log. On Fri, Aug 24, 2012 at 10:52 AM, Kevin Goess <kgo...@bepress.com> wrote: > On Fri, Aug 24, 2012 at 10:23 AM, Ahmet Arslan <iori...@yahoo.com> wrote: > >> > We have a pretty standard >> > out-of-the-box solr/jetty setup. Using the web >> > UI at /solr/admin/logging, for WARNING or SEVERE we get less >> > logging, but >> > none of CONFIG, FINE or FINEST result in any *more* logging >> > than just at >> > INFO. >> >Taken from solr-trunk/solr/example/README.txt >> >> "By default, Solr will log to the console. This can be convenient when >> first getting started, but eventually you will want to log to a file. To >> enable logging, you can just pass a system property to Jetty on startup: >> >> java -Djava.util.logging.config.file=etc/logging.properties -jar start.jar >> > > Thanks, Ahmet. We're actually fine capturing console logging to a file > right now. But are you saying that the FINEST/FINE/CONFIG levels on the > web ui at /solr/admin/logging/ won't work without a logging.config.file set > up ? > > > > > > -- > Kevin M. Goess > Software Engineer > Berkeley Electronic Press > kgo...@bepress.com > > 510-665-1200 x179 > www.bepress.com > > bepress: sustainable scholarly publishing -- Lance Norskog goks...@gmail.com
