Daniel,

If your objective is to turn on debug logging AND use your own property
files, my recommendation is to activate commons logging (see the README file
in CVS). Then in your my.properties replace:

services.LoggingService.default = debug

with ...

services.LoggingService.default = jetspeed
services.LoggingService.log4j.properties = /WEB-INF/conf/log4j.properties

Finally, modify default log4j.properties as follows:

log4j.rootLogger = DEBUG, jetspeed

The Turbine logging is going away shortly so I don't think that anyone will
want to invest time into fixing bug# 16781.

BTW: I know it would be nice to put the log4j overrides in your custom
mylog4j.properties and then include default log4j.properties. If someone can
get this to work, please let me know ;-)

Best regards,

Mark Orciuch - [EMAIL PROTECTED]
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/

> -----Original Message-----
> From: Daniel Freitag [mailto:[EMAIL PROTECTED]
> Sent: Sunday, July 13, 2003 9:56 AM
> To: jetspeed-user-list
> Subject: Problem with LoggingSErvice
>
>
> Hi,
>
> I have my own properties file and I have read the problem report no.
> 16781.
> (To remove the entry services.LoggingService.default = debug)
>
> After the removal of it tomcat doesn't start! If the entry is part of
> the file then it starts (and I get the error described in the pr.)
>
> I have no idea why tomcat hangs. The last message I see: Loading
> container servlet default
> Nothing more!
>
> Does anybody know the reason for this problem? (Or the solution? *g*)
> Daniel
>
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to