You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mirae-user@ws.apache.org by Aishwarya R <ai...@gmail.com> on 2006/11/21 21:09:55 UTC

Log4j problems in Tomcat 5.x

hello,
I switched from Tomcat 4 to 5, and ever since have had unsolvable
problems with logging. In short, the commons logger refuses to use
Log4j. This would be fine for Tomcat itself, but all of my classes that
use commons-logging get taken over in this way. i have moved my own
code to use Log4j directly (so I know it works, and is configured
correctly, and is in the classpath of the context), but all of my jars
that use commons are out of my control.
If I try and force commons to use log4j, ( with
org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogg
er in a commons-logging.properties file in /WEB-INF/classes), it gives
me a ClassNotFound exception, no matter where I place the log4j jar.
I have seen many messages on this list related to this issue, but no
solutions. Has anyone come up with anything? Aishwarya <http://www.chakpak.com>

Re: Log4j problems in Tomcat 5.x

Posted by Aishwarya R <ai...@gmail.com>.
Sorry, sent it the wrong mailing list.

On 11/22/06, Aishwarya R <ai...@gmail.com> wrote:
>
> hello,
> I switched from Tomcat 4 to 5, and ever since have had unsolvable
> problems with logging. In short, the commons logger refuses to use
> Log4j. This would be fine for Tomcat itself, but all of my classes that
> use commons-logging get taken over in this way. i have moved my own
> code to use Log4j directly (so I know it works, and is configured
> correctly, and is in the classpath of the context), but all of my jars
> that use commons are out of my control.
> If I try and force commons to use log4j, ( with  org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogg
> er in a commons-logging.properties file in /WEB-INF/classes), it gives
> me a ClassNotFound exception, no matter where I place the log4j jar.
> I have seen many messages on this list related to this issue, but no
> solutions. Has anyone come up with anything? Aishwarya www.chakpak.com
>
>