Hi Ryan, Thanks for the inputs .These are the set of steps followed to solve this issue. 1.make a loggging property file say solrLogging.properties.We can copy the default logging property file available at JAVA_HOME/jre/lib folder. default java logging file will look like the following. ############################################################ # Default Logging Configuration File # # You can use a different file by specifying a filename # with the java.util.logging.config.file system property. # For example java -Djava.util.logging.config.file=myfile ############################################################
############################################################ # Global properties ############################################################ # "handlers" specifies a comma separated list of log Handler # classes. These handlers will be installed during VM startup. # Note that these classes must be on the system classpath. # By default we only configure a ConsoleHandler, which will only # show messages at the INFO and above levels. handlers= java.util.logging.ConsoleHandler # To also add the FileHandler, use the following line instead. #handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler # Default global logging level. # This specifies which kinds of events are logged across # all loggers. For any given facility this global level # can be overriden by a facility specific level # Note that the ConsoleHandler also has a separate level # setting to limit messages printed to the console. .level= INFO ############################################################ # Handler specific properties. # Describes specific configuration info for Handlers. ############################################################ # default file output is in user's home directory. java.util.logging.FileHandler.pattern = %h/java%u.log java.util.logging.FileHandler.limit = 50000 java.util.logging.FileHandler.count = 1 java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter # Limit the message that are printed on the console to INFO and above. java.util.logging.ConsoleHandler.level = INFO java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter ############################################################ # Facility specific properties. # Provides extra control for each logger. ############################################################ # For example, set the com.xyz.foo logger to only log SEVERE # messages: com.xyz.foo.level = SEVERE To prevent INFO level messages change java.util.logging.ConsoleHandler.level = INFO to java.util.logging.ConsoleHandler.level = SEVERE 2.While starting the server for Ex. Jboss add the following line to the run.bat or run.sh set JAVA_OPTS=%JAVA_OPTS% -Djava.util.logging.config.file=Y:\solrLog.properties This will solve the issue Regards, Rinesh. ryantxu wrote: > > solr 1.3 uses java logging. Most app containers (tomcat, resin, etc) > give you a way to configure that. Also check: > http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/overview.html#1.8 > > You can make runtime changes from the /admin/ logging tab. However, > these changes are not persisted when the app restarts. > > > On Dec 15, 2008, at 11:52 PM, Rinesh1 wrote: > >> >> Hi, >> I was trying to do a performance test on Solr web application. >> If I run the performance tests, lot og logging is happening due >> to which >> I am getting log files in GBs >> Is there any clean way of deactivating logging or changing the >> log level >> to say error .. >> Is there any property file for the same. >> Please give your inputs for the same. >> Regards, >> Rinesh. >> >> -- >> View this message in context: >> http://www.nabble.com/Details-on-logging-in-Solr-tp21027267p21027267.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> > > > -- View this message in context: http://www.nabble.com/Details-on-logging-in-Solr-tp21027267p21027540.html Sent from the Solr - User mailing list archive at Nabble.com.
