: Yes, I do see the logs printed to the console. Since it's a unix : box, I then close the terminal after starting up solr. When a problem : happens, such as that solr no longer responds, I hope to be able to : to check the log files to see what happened.
ah ... okay, i understand where you are coming from. at a minimum i would change your "startup" methodology to include redirecting stderr/stdour to afile so you don't completley lose the console when closing the terminal used to start the process. but in general i would look into how to configure java standard logging of webapps in Jetty .. the settings you found in the jetty.xml probably only relate to logging from the core Jetty classes. : It's probably a Java logger setting problem. I just saw Brian's reply. : I'll give that a try. his suggestions looked like they make sense for standalone java apps, but when running in a servlet container it may not always work -- the servlet container is totally within it's purview to do things that may prevent techniques like that from working. breifly skimming this webpage leads me to believe Jetty won't interfeer with any JDK logging properties you may choose to set, so it would probably work fine. http://jetty.mortbay.org/jetty5/tut/logging.html -Hoss
