Hi Joe!
As far as I know, Juli is a weak logging system. For instance, I haven't
found any rolling file appenders, so my logs grew endlessly. I will not be
surprised if it doesn't support optional package loading. I reccomend you to
switch to Log4j or something.
Andrey
2009/6/12 Joe Baldwin <jfbaldwi..arthlink.net>
> Andrus,
>
> I did quite a few tests yesterday and still cannot determine whether the
> Tomcat logging.properties method will ever work.
>
> The directives that seem to work are as follows:
>
> handlers = org.apache.juli.FileHandler
> org.apache.juli.FileHandler.directory = ${catalina.base}/logs
> org.apache.juli.FileHandler.prefix = mywebapp.
> org.apache.juli.FileHandler.level = WARN
>
> The last line will turns off all logging. If this is changed to "INFO"
> then logging is turned on. However, I cannot get the cayenne "QueryLogger",
> "conf", or "util" directives to work. It may be my syntax (using juli), or
> it may be that Tomcat juli will not disseminate the directives, or it may be
> that it just cannot be done with juli logging.properties.
>
> Thanks,
> Joe
>
>
>
> On Jun 12, 2009, at 2:12 AM, Andrus Adamchik wrote:
>
>
>> On Jun 11, 2009, at 11:05 PM, Joe Baldwin wrote:
>>
>> Question:
>>> Is is possible that the Cayenne hard-coded defaults (which I read about
>>> somewhere in your docs), are over-riding my loggin.properties?
>>>
>>
>> Actually no. Cayenne (or your application code) would log something with a
>> certain priority. A logging framework decides whether a given priority
>> should be logged or ignored. I have very little experience with the new
>> Tomcat "juli" logger. So another random thing to try: instead of OFF, can
>> you try WARN (Cayenne logs everything with level INFO, so WARN should
>> suppress the logging).
>>
>> Andrus
>>
>
>
This archive was generated by hypermail 2.0.0 : Sat Jun 13 2009 - 02:10:46 EDT