[
https://issues.jboss.org/browse/SOLDER-119?page=com.atlassian.jira.plugin...
]
Lincoln Baxter III commented on SOLDER-119:
-------------------------------------------
{code}(03:09:40 PM) maschmid: lincolnthree, re SOLDER-119, add "Dependencies:
org.jboss.logging,org.jboss.logmanager" to any manifest in war...{code}
Looks like we need to see if we can do this in the JAR itself. Though, I'd think we
should avoid the need for this if possible. When was this introduced?
CNFE org.jboss.logmanager.Logger$AttachmentKey on AS7
-----------------------------------------------------
Key: SOLDER-119
URL:
https://issues.jboss.org/browse/SOLDER-119
Project: Seam Solder
Issue Type: Bug
Components: Logging
Affects Versions: 3.1.0.Beta1
Environment: jboss-as-7.1.0.Alpha1-SNAPSHOT
Reporter: Marek Schmidt
Assignee: Ken Finnigan
Priority: Blocker
Deployment of a WAR with Seam Solder 3.1.0.Beta1 (such as, Seam Config princess rescue
example) fails on AS7.
The application contains the following seam jars and no other libraries:
{noformat}
seam-config-xml-3.1.0.Beta1.jar
seam-solder-3.1.0.Beta1.jar
seam-solder-api-3.1.0.Beta1.jar
seam-solder-logging-3.1.0.Beta1.jar
{noformat}
{noformat}
14:52:59,707 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."config-princess-rescue.war".POST_MODULE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."config-princess-rescue.war".POST_MODULE: Failed to
process phase POST_MODULE of deployment "config-princess-rescue.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_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
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.solder.logging.Logger.<init>(Logger.java:44)
at org.jboss.seam.solder.logging.Logger.getLogger(Logger.java:1965)
at org.jboss.seam.solder.logging.Logger.getLogger(Logger.java:1991)
at
org.jboss.seam.solder.bean.defaultbean.DefaultBeanExtension.<clinit>(DefaultBeanExtension.java:81)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [:1.6.0_24]
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[:1.6.0_24]
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[:1.6.0_24]
at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_24]
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.config-princess-rescue.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
14:52:59,710 INFO [org.jboss.as.server.controller] (pool-2-thread-6) Deployment of
"config-princess-rescue.war" was rolled back with failure message {"Failed
services" =>
{"jboss.deployment.unit.\"config-princess-rescue.war\".POST_MODULE"
=> "org.jboss.msc.service.StartException in service
jboss.deployment.unit.\"config-princess-rescue.war\".POST_MODULE: Failed to
process phase POST_MODULE of deployment \"config-princess-rescue.war\""}}
14:52:59,711 INFO [org.jboss.as.controller] (pool-2-thread-6) Service status report
Services which failed to start:
service jboss.deployment.unit."config-princess-rescue.war".POST_MODULE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."config-princess-rescue.war".POST_MODULE: Failed to
process phase POST_MODULE of deployment "config-princess-rescue.war"
14:52:59,728 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped
deployment config-princess-rescue.war in 14ms
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira