Problem Verifying WAR Using Log4J on 3.2.3

hunterhillegas Mar 10, 2004 6:00 PM

Since trying 3.2.3, our WAR files that use Log4J don't deploy.

I get verifier errors like this:

15:20:52,954 ERROR [Engine] ----- Root Cause -----
java.lang.VerifyError: (class: org/apache/log4j/Category, method: getRoot signature: ()Lorg/apache/log4j/Category;) Wrong return type in function
at startupServlet.init(Unknown Source)

Huh?

The code we're using to initialize log4j is:
//logging
cat = Category.getInstance(siteConfig.getClientName() + ": Name");

This has worked fine in 3.0.x and 3.x releases...

Any ideas what's going on?

1. Re: Problem Verifying WAR Using Log4J on 3.2.3

starksm64 Mar 15, 2004 8:12 PM (in response to hunterhillegas)
There is a conflict with the loaded log4j.jar version coming from somewhere. If your bundling your own log4j.jar in the web and need this version, then you have to enable class loader overrides using a jboss-web.xml setup like:

<jboss-web> <class-loading java2ClassLoadingCompliance="false"> <loader-repository> jboss.test:war=log4j113.war <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> </class-loading> </jboss-web>
Actions
2. Re: Problem Verifying WAR Using Log4J on 3.2.3

mlueck May 12, 2004 2:37 AM (in response to hunterhillegas)

Hello Scott,

I also experienced a "java.lang.VerifyError " and the reason seems to be that there are two Jar's with different versions in two different webapps. What I don't understand in your example-configuration is this line:

>
> jboss.test:war=log4j113.war
>

Is this a symbolic name or do I have to use the name of my war-file here?

Greetings from Germany
Matthias Lueck
Actions
3. Re: Problem Verifying WAR Using Log4J on 3.2.3

juha May 15, 2004 12:38 AM (in response to hunterhillegas)

You can use any object name.
Actions

Go to original post