log4j version 1.2.0 released
I do have multiple log4j.jar files around, but all are of the same
version. There is reason to believe that I may have multiple different
versions of -my own- class files lying around that I should hunt down.
After some further hunting, the original exception
Try the following test program. Compile it using the same compiler
that produced the binary that generated the VerifyError. Put the same
log4j.jar file on the classpath. (The one that was used when the
VerifyError was thrown.)
import org.apache.log4j.BasicConfigurator;
import
Basic summary:
It was due to having both log4j.jar and
org.apache.log4j.spi.ThrowableInformation.class
As I mentioned in the previous email, I was concerned I had multiple
versions of my own code. In the process of removing those extra
versions I discovered that JBuilder6 had been
At 07:45 24.05.2002 -0700, Kevin Steppe wrote:
Basic summary:
It was due to having both log4j.jar and
org.apache.log4j.spi.ThrowableInformation.class
As I mentioned in the previous email, I was concerned I had multiple
versions of my own code. In the process of removing those extra
When I use log4j to log message and stack info when
Class.forName().newInstance() fails I get an Error thrown. I thought
log4j was supposed to guarentee this didn't happen?
Here is the error:
java.lang.VerifyError: (class:
org/apache/log4j/spi/ThrowableInformation, method: getThrowableStrRep
