Will, I'd be definitely interested in your code but mostly in the config & deployment options if you can share.
You did not happen to deploy on Websphere 6 by any chance ? I can't find a way to configure jul to only log into our application logs (even less so in our log4j logs); I'm not even sure it is feasible since IBMs documentation state that only "anonymous" loggers can escape the common sink. And since commons logging is in our bundled war for some other library, things get a tad confusing on where/what the actual configuration should be. I realize this is not the first thread on the logging topic but we've not been able (yet) to gather some experience or collect documented way of doing this for each container (Jetty/Tomcat5/Tomcat6/WebLogic/webSphere...). This is why I tend to prefer the container agnostic way of configuring logging (and else), the application/war configured way. This lead me to https://issues.apache.org/jira/browse/SOLR-549 SOLR-549 which is cross-container but (alas) requires the code to change and introduces (yet another) logging configuration convention. Henri Will Johnson-2 wrote: > > Henri, > > There are some bridges out there but none had a version number > 0.1. I > found the simplest way was to configure JUL using a custom config file and > then tell it to use my custom handler to forward all messages to log4j. > There are obvious performance implications but it is doable and fairly > simple since it didn't require any solr code changes. > > - will > -- View this message in context: http://www.nabble.com/logging-through-log4j-tp16825424p16847405.html Sent from the Solr - User mailing list archive at Nabble.com.
