you can also change the priorities programaticaly from your application:
Logger.setLevel(Level level);
maybe this is done within quarz??? (i doubt it)
this is IMO not recomendable because it is not obvious and not changable
without recompilation.
so for the original poster:
1) are you 100% sure that you are editing the log4j.properties that is used?
(additivity IMO only has to be set to false if you only want it on one
appender)
2) otherwise maybe the priority is changed within the application (or within
any of it's libraries...) you can try to change this runtime:
Logger.getLogger("org.quartz").setLevel(Level.ERROR);
of course anybody could change this at anytime, so no guaranties...
> -----Ursprüngliche Nachricht-----
> Von: Peter Neu [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 29. August 2006 10:24
> An: 'Log4J Users List'
> Betreff: AW: HowTo Disable Logging Output for classes using
> commons.logging
>
>
> I have experimented with a log4j.xml entry that looks like this:
>
> <category name="org.quartz" additivity="false">
> <priority value="ERROR" />
> <appender-ref ref="logfile"/>
> <appender-ref ref="cons"/>
> </category>
>
> But this does not help...
>
> I use the product lambda probe (tomcat monitor) they also use
> quartz somehow
> they managed to turn the quartz logging off. They don't have any
> modifications in the log4j.properties file. I don't see how
> they could do
> it.
>
> Cheers,
> Pete
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
