logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Randall <javabr...@gmail.com>
Subject Re: FileAppender is not assignable to Appender
Date Mon, 02 Nov 2009 12:00:09 GMT
Log4j is identifying the classloaders with incompatible versions of the
classes referenced.  The classpaths are missing so hard for me to deduce
more, but you may be able to determine which WAS classloaders in the
webapp's classloader hierarchy have been responsible for loading the
incompatible versions, which may lead to the reason why this is occuring.

If you are running log4j 1.2.6 or later try setting system property
log4j.ignoreTCL=true to tell log4j to not-prefer the thread context


On Sun, Nov 1, 2009 at 2:41 PM, chrisgage <chrisgage@bellsouth.net> wrote:

> This project started using Spring (and its dependency on commons logging)
> back in June 2007, but this problem only started this summer, two years
> later.  In those two years it has grown to 200 JSPs and over 1000 classes
> so
> it's hard to find an error that refuses to say exactly where it was
> created.
> But I do appreciate the contribution, and will check it out...
> javabrett wrote:
> >
> > Check whether the added JARs include Commons Logging. I notice that the
> > Appender is named after Spring. Spring depends on Commons Logging which
> is
> > notorious for creating classloading challenges.
> >
> --
> View this message in context:
> http://old.nabble.com/FileAppender-is-not-assignable-to-Appender-tp26095007p26148077.html
> Sent from the Log4j - Users mailing list archive at Nabble.com.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message