My guess: there are two log4j.jar, probably of different versions: one in the
parent classlaoder and one in the child classloader. Therefore java regards
these two as different classes.
Heri
-Ursprüngliche Nachricht-
Von: chrisgage [mailto:chrisg...@bellsouth.net]
Gesendet: Mittwoch,
You cannot cast it. But if you instantiate the commons Logger with the same
name as your log4j logger your log statements will end up in the same logger
instance (log4j Logger). Commons logging is only a wrapper, and instantiates
log4j if it finds a log4j.jar in the classpath (and not
Dear All!
I encountered a problem I do not really see how to resolve. I want to assign
a unique port for every instance of an object I have, but I am not able to
assign a port for the SocketAppender I use, because when I set the new port,
it won't reconnect (jsut set the port variable), thus the
did you try calling activateOptions method on the appender?
On Thu, Oct 29, 2009 at 12:07 PM, Mate Gulyas avalo...@gmail.com wrote:
Dear All!
I encountered a problem I do not really see how to resolve. I want to
assign
a unique port for every instance of an object I have, but I am not able
That was what I thought originally. But that isn't it...
The jars we added definitely do not contain a log4j.jar, (I have checked the
source and unzipped the jar files to be sure) and the only one in the
workspace is log4j-1.2.15.jar in the lib folder of the EAR project. And all
the jar
Hi,
I'm using log4j 1.2.9 and a while after normal activity, stops logging to
the file. The application is still functioning correctly though. At
first I thought the application went down, but after investigation, the
application was still up and running correctly.
Here is my environment and
