I did what it says here
http://minaret.biz/tips/log4j.html
but no results.
I havn't found other decent "instructions" yet.
PK
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
lse who is interested) the sources and/or war.
PM me off-list.
Tim
> -Original Message-
> From: Peter Kennard [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 07, 2007 10:59 AM
> To: Tomcat Users List
> Subject: Re: Console Logging
>
> I did what it says here
>
Thanks will check out after lunch. I definately want to use the
log4j for our apps.
I am assuming the Tomcat internals have very good debug log info like
why sockets are closed or timed out etc (If I can get them activated
:) I dread finding out it might be a windows sockets bug :|
PK
At
-Original Message-
> From: Peter Kennard [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 07, 2007 10:59 AM
> To: Tomcat Users List
> Subject: Re: Console Logging
>
> I did what it says here
> http://minaret.biz/tips/log4j.html
> but no results.
>
> I havn't
BTW found the bug it wasn't in tomcat ;^> but in the client :)
In any case the logger info was very helpful!
PK
At 13:18 3/7/2007, you wrote:
> I did what it says here
> http://minaret.biz/tips/log4j.html
> but no results.
>
> I havn't found other decent "instructions" yet.
> PK
>
try this one
