Logging settings problem in Seam 3 application on JBoss 7
hantsy Aug 30, 2011 4:35 AMI modified the seam3 dependencies version to 3.1.0.Beta2, and I have added solder-logging to dependencies...
16:27:29,141 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."siorc.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."siorc.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "siorc.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] Caused by: java.lang.NoClassDefFoundError: org/jboss/logmanager/Logger$AttachmentKey at org.jboss.seam.solder.logging.internal.JBossLogManagerProvider.<clinit>(JBossLogManagerProvider.java:36) at org.jboss.seam.solder.logging.internal.LoggerProviders.findProvider(LoggerProviders.java:33) at org.jboss.seam.solder.logging.internal.LoggerProviders.<clinit>(LoggerProviders.java:28) at org.jboss.seam.solder.logging.internal.Logger.getLogger(Logger.java:2164) at org.jboss.seam.logging.Logger.<init>(Logger.java:44) at org.jboss.seam.logging.Logger.getLogger(Logger.java:1965) at org.jboss.seam.logging.Logger.getLogger(Logger.java:1991) at org.jboss.seam.config.xml.bootstrap.XmlConfigExtension.<clinit>(XmlConfigExtension.java:68) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [:1.6.0_27] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [:1.6.0_27] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [:1.6.0_27] at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_27] at org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.loadExtension(WeldPortableExtensionProcessor.java:117) at org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.loadAttachments(WeldPortableExtensionProcessor.java:100) at org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.deploy(WeldPortableExtensionProcessor.java:86) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Logger$AttachmentKey from [Module "deployment.siorc.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:330) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101) ... 21 more
I had added jboss logging to dependencies, it is still there.
<dependency> <groupId>org.jboss.logging</groupId> <artifactId>jboss-logging-spi</artifactId> <version>2.1.2.GA</version> </dependency> <dependency> <groupId>org.jboss.logging</groupId> <artifactId>jboss-logging-log4j</artifactId> <version>2.1.2.GA</version> </dependency>
When I changed jboss-logging-log4j to jboss-logging-logmanager, the exception required set a property to use the java.util.logging...
Why on Jboss 6 and Jboss 7 there are so much troubles, I have tried on jboss 6(I can not added my sf4l and log4j)...why in my application I can not controlled them directly as other application server???