r 2007 17:29
To: Tomcat Users List
Subject: Re: Embedded Apache Tomcat/5.5.9 outputting to
java.util.logging instead of console
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
The OP is using embedded TC, so there's no script.
> Magnus Vojbacke (KA/EAB) wrote:
>>> Are the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
The OP is using embedded TC, so there's no script.
> Magnus Vojbacke (KA/EAB) wrote:
>>> Are they inspecting catalina.out? If so, what will stop them from
>>>
>> reading whatever /other/ logfile you choose?
>>
>> No, there _is_ no catalin
Magnus Vojbacke (KA/EAB) wrote:
Are they inspecting catalina.out? If so, what will stop them from
reading whatever /other/ logfile you choose?
No, there _is_ no catalina.out anywhere in my tomcat folder or the child
folders thereof. Everything is output to console. Probably should have
men
> Are they inspecting catalina.out? If so, what will stop them from
reading whatever /other/ logfile you choose?
No, there _is_ no catalina.out anywhere in my tomcat folder or the child
folders thereof. Everything is output to console. Probably should have
mentioned that, since it's a little weird
Chris is correct, Tomcat will use java.util.logging if it doesn't find log4j
(and TC 6 won't even look for log4j by default). So all you have to do is
to configure java.util.logging for your application. If you want to use
Tomcat's Juli implementation, then you need to configure that for your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Magnus,
Magnus Vojbacke (KA/EAB) wrote:
> Although the warnings do not affect the
> performance of our product, they are confusing to our users.
Are they inspecting catalina.out? If so, what will stop them from
reading whatever /other/ logfile you ch
