Further to this problem, we built JBoss 2.4.0 with the log4j1.2beta2 (instead of
the v1.1.3 they used).
This created a build error. Compile error below.
JBoss uses its own Logger class which is a wrapper on top of the Category class.
It seems a namespace conflict is occuring.
The easiest fix is to specifically the fully qualified name of the Logger class
whereever I use it in my own code.
Even better would be for the JBoss group to modify theirs as it conflicts with
log4j1.2 .
I'll notify them via a separate email post.
Regards,
T Master
Compile error of JBoss 3.0beta2 with new log4j.jar:
12:28:59,854 ERROR +AFs-Server+AF0- start failed
java.lang.NoSuchMethodError
at org.jboss.logging.Logger.isDebugEnabled(Logger.java:88)
at
org.jboss.system.server.ServerImpl.initBootLibraries(ServerImpl.java:
314)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:228)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:174)
at org.jboss.Main.boot(Main.java:307)
at org.jboss.Main+ACQ-1.run(Main.java:326)
at java.lang.Thread.run(Thread.java:484)
java.lang.NoSuchMethodError
at org.jboss.logging.Logger.isDebugEnabled(Logger.java:88)
at
org.jboss.system.server.ServerImpl.initBootLibraries(ServerImpl.java:
314)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:228)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:174)
at org.jboss.Main.boot(Main.java:307)
at org.jboss.Main+ACQ-1.run(Main.java:326)
at java.lang.Thread.run(Thread.java:484)
----- Original Message -----
From: +ACI-T Master+ACI- +ADw-tmaster+AEA-iknowledge.com+AD4-
To: +ADw-log4j-user+AEA-jakarta.apache.org+AD4-
Sent: Thursday, February 28, 2002 11:46 AM
Subject: jboss 2.4.0 and 3.0beta2 and log4j v1.2 beta2 problems
+AD4- Has anyone run into problems with JBoss2.4.0 and JBoss3.0beta2 using
log4j
+AD4- v1.2 ?
+AD4-
+AD4- JBoss2.4.0 and JBoss3.0 both log4j1.1.3 internally, and whereever the
log4j1.2
+AD4- jar is placed in the war file, the Logger cannot be found). I'm not sure if
+AD4- this is just a classpath issue.
+AD4-
+AD4- So, we tried replacing their log4j1.1.3 jar with the log4j1.2beta2 jar
+AD4- our code uses.
+AD4- This was done with JBoss2.4.0 and JBoss3.0beta2 .
+AD4- Exceptions were produced, and these are pasted below.
+AD4-
+AD4- +AFs-1+AF0-
+AD4- Stack trace from JBoss2.4.0 - having its log4j1.1.3 jar replaced
by
+AD4- log4j1.2beta2 jar.
+AD4-
+AD4- java.lang.NoSuchFieldError: priority
+AD4- at
org.jboss.logging.log4j.ConsoleAppender.append(ConsoleAppender.java:6
+AD4- 4)
+AD4- at
org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
+AD4-
+AD4- at
org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders
+AD4- (AppenderAttachableImpl.java:57)
+AD4- at org.apache.log4j.Category.callAppenders(Category.java:199)
+AD4- at org.apache.log4j.Category.forcedLog(Category.java:392)
+AD4- at org.apache.log4j.Category.log(Category.java:852)
+AD4- at org.jboss.logging.Logger.info(Logger.java:133)
+AD4- at org.jboss.util.Info.preRegister(Info.java:42)
+AD4- at
com.sun.management.jmx.MBeanServerImpl.preRegisterInvoker(MBeanServer
+AD4- Impl.java:2245)
+AD4- at
com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.ja
+AD4- va:513)
+AD4- at javax.management.loading.MLet.getMBeansFromURL(MLet.java:523)
+AD4- at javax.management.loading.MLet.getMBeansFromURL(MLet.java:369)
+AD4- at org.jboss.Main.+ADw-init+AD4-(Main.java:180)
+AD4- at org.jboss.Main+ACQ-1.run(Main.java:110)
+AD4- at java.security.AccessController.doPrivileged(Native Method)
+AD4- at org.jboss.Main.main(Main.java:106)
+AD4-
+AD4-
+AD4-
+AD4-
+AD4- +AFs-2+AF0-
+AD4- Stack trace from JBoss3.0 beta2 - having its log4j1.1.3 jar
+AD4- replaced by log4j1.2beta2 jar.
+AD4- Same as +AFs-1+AF0-.
+AD4-
+AD4-
+AD4-
+AD4- +AFs-3+AF0-
+AD4- Stack trace from JBoss3.0 beta2 - adding log4j1.2beta2 jar to
the
+AD4- classpath of the war (tried all locations)
+AD4- .
+AD4- java.lang.VerifyError: (class: org/apache/log4j/LogManager, method:
++ADw-clinit+AD4-
+AD4- signature: ()V) Incompatible argument to function
+AD4- at org.apache.log4j.Logger.getLogger(Logger.java:101)
+AD4- .
+AD4- . +ADw-my company code and methods+AD4-
+AD4- .
+AD4- at java.lang.Class.newInstance0(Native Method)
+AD4- at java.lang.Class.newInstance(Class.java:237)
+AD4- at
+AD4-
org.jboss.verifier.strategy.AbstractVerifier.hasDefaultConstructor(AbstractVerif
+AD4- ier.java:383)
+AD4- at
+AD4-
org.jboss.verifier.strategy.EJBVerifier11.verifySessionBean(EJBVerifier11.java:6
+AD4- 30)
+AD4- at
+AD4- org.jboss.verifier.strategy.EJBVerifier11.checkSession(EJBVerifier11.java:93)
+AD4- at org.jboss.verifier.BeanVerifier.verify(BeanVerifier.java:137)
+AD4- at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:365)
+AD4- at org.jboss.deployment.MainDeployer.create(MainDeployer.java:603)
+AD4- at org.jboss.deployment.MainDeployer.create(MainDeployer.java:597)
+AD4- at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:515)
+AD4- at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:496)
+AD4- at org.jboss.deployment.MainDeployer.scan(MainDeployer.java:317)
+AD4- at org.jboss.deployment.MainDeployer.startService(MainDeployer.java:247)
+AD4- at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162)
+AD4- at java.lang.reflect.Method.invoke(Native Method)
+AD4- at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
+AD4- at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
+AD4- at
+AD4-
org.jboss.system.ServiceController+ACQ-ServiceProxy.invoke(ServiceController.java:77
+AD4- 9)
+AD4- at +ACQ-Proxy0.start(Unknown Source)
+AD4- at org.jboss.system.ServiceController.start(ServiceController.java:343)
+AD4- at java.lang.reflect.Method.invoke(Native Method)
+AD4- at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
+AD4- at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
+AD4- at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:291)
+AD4- at org.jboss.system.server.ServerImpl.start(ServerImpl.java:174)
+AD4- at org.jboss.Main.boot(Main.java:307)
+AD4- at org.jboss.Main+ACQ-1.run(Main.java:326)
+AD4- at java.lang.Thread.run(Thread.java:484)
+AD4-
+AD4-
+AD4- Does anyone have clues to get JBoss working with the new log4j v1.2 jar?
+AD4- Help/Tips/Thoughts on either the classpath issue or integrating the log4j1.2
+AD4- jar file into JBoss would be extrmely appreciated.
+AD4-
+AD4-
+AD4- T Master
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
