Has anyone run into problems with   JBoss2.4.0 and JBoss3.0beta2   using   log4j
v1.2 ?

JBoss2.4.0 and  JBoss3.0 both  log4j1.1.3 internally, and whereever the log4j1.2
jar is placed in the war file, the Logger cannot be found).  I'm not sure if
this is just a classpath issue.

So, we tried replacing their   log4j1.1.3 jar   with the   log4j1.2beta2 jar
our code uses.
This was done with   JBoss2.4.0  and   JBoss3.0beta2 .
Exceptions were produced, and these are pasted below.

+AFs-1+AF0-
            Stack trace from JBoss2.4.0 - having its log4j1.1.3 jar replaced by
log4j1.2beta2 jar.

java.lang.NoSuchFieldError: priority
        at org.jboss.logging.log4j.ConsoleAppender.append(ConsoleAppender.java:6
4)
        at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)

        at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders
(AppenderAttachableImpl.java:57)
        at org.apache.log4j.Category.callAppenders(Category.java:199)
        at org.apache.log4j.Category.forcedLog(Category.java:392)
        at org.apache.log4j.Category.log(Category.java:852)
        at org.jboss.logging.Logger.info(Logger.java:133)
        at org.jboss.util.Info.preRegister(Info.java:42)
        at com.sun.management.jmx.MBeanServerImpl.preRegisterInvoker(MBeanServer
Impl.java:2245)
        at com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.ja
va:513)
        at javax.management.loading.MLet.getMBeansFromURL(MLet.java:523)
        at javax.management.loading.MLet.getMBeansFromURL(MLet.java:369)
        at org.jboss.Main.+ADw-init+AD4-(Main.java:180)
        at org.jboss.Main+ACQ-1.run(Main.java:110)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.jboss.Main.main(Main.java:106)




+AFs-2+AF0-
            Stack trace from JBoss3.0 beta2   - having its log4j1.1.3 jar
replaced by log4j1.2beta2 jar.
Same as +AFs-1+AF0-.



+AFs-3+AF0-
            Stack trace from JBoss3.0 beta2   - adding log4j1.2beta2 jar to the
classpath of the war (tried all locations)
.
java.lang.VerifyError: (class: org/apache/log4j/LogManager, method: +ADw-clinit+AD4-
signature: ()V) Incompatible argument to function
 at org.apache.log4j.Logger.getLogger(Logger.java:101)
.
. +ADw-my company code and methods+AD4-
.
 at java.lang.Class.newInstance0(Native Method)
 at java.lang.Class.newInstance(Class.java:237)
 at
org.jboss.verifier.strategy.AbstractVerifier.hasDefaultConstructor(AbstractVerif
ier.java:383)
 at
org.jboss.verifier.strategy.EJBVerifier11.verifySessionBean(EJBVerifier11.java:6
30)
 at
org.jboss.verifier.strategy.EJBVerifier11.checkSession(EJBVerifier11.java:93)
 at org.jboss.verifier.BeanVerifier.verify(BeanVerifier.java:137)
 at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:365)
 at org.jboss.deployment.MainDeployer.create(MainDeployer.java:603)
 at org.jboss.deployment.MainDeployer.create(MainDeployer.java:597)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:515)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:496)
 at org.jboss.deployment.MainDeployer.scan(MainDeployer.java:317)
 at org.jboss.deployment.MainDeployer.startService(MainDeployer.java:247)
 at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162)
 at java.lang.reflect.Method.invoke(Native Method)
 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
 at
org.jboss.system.ServiceController+ACQ-ServiceProxy.invoke(ServiceController.java:77
9)
 at +ACQ-Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:343)
 at java.lang.reflect.Method.invoke(Native Method)
 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:291)
 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)


Does anyone have clues to get JBoss working with the new log4j v1.2 jar?
Help/Tips/Thoughts on either the classpath issue or integrating the log4j1.2
jar file into JBoss  would be extrmely appreciated.


T Master



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to