On Aug 29, 2006, at 9:08 AM, Peter Neu wrote:

I assume yes. The jar file contains only the root package org.qartz.
Everything else is located beneath..


Logger names are determined by the arguments to calls to Logger.getLogger(). They have no fixed relationship to the class names in the application. They are frequently the same as class names, but do not have to be. It would be helpful if you could provide examples of the logging messages that are showing up in your log files that you think should not be showing up. They would likely contain the logger name which would allow us to confirm your assumption and identify what particular log requests to investigate.


In my opinion a declaration like this should suffice:

log4j.category.org.quartz=info, file

or

<logger name="org.quartz">
                <level value="info"/>
                <appender-ref ref="file"/>      
        </logger>

If the Quartz developers used a different set of logger names or you are editing a configuration file that is not being used, then your wishful thinking doesn't matter.

I have no idea what could be wrong. :o(



Several possibilities have been mentioned:

1. You are modifying a log4j.properties file that is not being used to configure the application. You could check that by changing a file name or something else and observe if the change was effective.

2, You are changing the level of a logger that is not being used by the application. Review the log file to see if the logger names appear in the log file and confirm that the logger names begin with "org.quartz."

3. (Less likely) The application explicitly changes the level of the logger overriding the configuration.

Since you are having the problem and have much better resources to investigate, it is your responsibility to do the simple tests to figure which if any apply. Asking on the Quartz-developer list might be more effective. Asking us here is asking us to guess what might be going wrong in two higher level frameworks (Quartz and commons- logging) that we do not have the same level of familiarity as we do in log4j.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to