Bugs item #983462, was opened at 2004-07-01 22:31 Message generated for change (Comment added) made by clli You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=983462&group_id=22866
Category: None Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Domosi Janos (domosi) Assigned to: Nobody/Anonymous (nobody) Summary: Classloader (?) problem in 3.2.4. and 3.2.5 Initial Comment: A full decsription of the problem: http://www.jboss.org/index.htmlmodule=bb&op=viewtopi c&p=3840616#3840616 Deployment crashes if we place commons-logging.jar into an .ear file (and registerer it with the META- INF/application.xml file) java.lang.NoSuchMethodException: org.apache.commons.modeler.BaseModelMBean.setDocBa se(java.lang.String)) at org.jboss.mx.server.ReflectedDispatcher.handleInvocatio nExceptions(ReflectedDispatcher.java:91) at org.jboss.mx.server.ReflectedDispatcher.dispatch (ReflectedDispatcher.java:64) at org.jboss.mx.server.Invocation.dispatch (Invocation.java:61) at org.jboss.mx.server.Invocation.dispatch (Invocation.java:53) at org.jboss.mx.server.Invocation.invoke (Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke (AbstractMBeanInvoker.java:185) at org.jboss.mx.server.MBeanServerImpl.invoke (MBeanServerImpl.java:473) at org.jboss.system.ServiceController$ServiceProxy.invoke (ServiceController.java:837) at $Proxy17.start(Unknown Source) at org.jboss.system.ServiceController.start (ServiceController.java:367) at sun.reflect.GeneratedMethodAccessor6.invoke (Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch (ReflectedDispatcher ---------------------------------------------------------------------- Comment By: Richard C. L. Li (clli) Date: 2004-07-13 13:47 Message: Logged In: YES user_id=735048 This problem can be reproduceable by using JBoss 3.2.3 with the Tomcat 5.0 SAR for JBoss 3.2.3. It seems the new tomcat breaks the classloading mechanism in JBoss. This is a quite annoying bug, and may have some other hidden problems which may not be found out yet. It just breaks all my STRUTS based web applications. ---------------------------------------------------------------------- Comment By: Stuart Herring (mabinogi) Date: 2004-07-06 09:09 Message: Logged In: YES user_id=34785 We have what may be a related problem.... we have commons-logging in the WEB-INF/lib directory of a .war file. It works fine if you just deploy the war file, and also works if you deploy it in a .ear file. But if you put a <loader-repository> entry in the jboss-app file to enforce a separate class loader for the ear, then it throws the following exception - 10:59:59,912 ERROR [Engine] ----- Root Cause ----- java.lang.ExceptionInInitializerError at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at <...snip...> org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:212) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:191) Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395) at au.com.hpa.test.TestServlet.<clinit>(TestServlet.java:18) ... 80 more Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525) ... 84 more Caused by: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:412) ... 85 more In this case it's something that only happens with 3.2.5 - 3.2.4 is not affected. ---------------------------------------------------------------------- Comment By: Michael Lipp (drmlipp) Date: 2004-07-05 15:13 Message: Logged In: YES user_id=731113 You get the same failure if you simply have commons-logging.jar in an EJB's classpath. We have an ejb.jar that references in its manifest's classpath-statement the commons-logging.jar packed in the ear; we observe the same behaviour. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=983462&group_id=22866 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
