|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
_______________________________________________ weld-issues mailing list [email protected] https://lists.jboss.org/mailman/listinfo/weld-issues
hi,
we have the same problem in our applications on JBoss 7.1.3.Final (Weld 1.1.9.Final).
the stack trace is:
{25.03.2013 11:24:37,109 ERROR [ org.jboss.msc.service.fail] ([MSC service thread 1]) MSC00001: Failed to start service jboss.deployment.unit."myapp1.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."myapp1.war".WeldService: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class a.b.c.myapp1.beans.Preferences] with qualifiers [@Any @Default] at org.jboss.as.weld.services.WeldService.start(WeldService.java:83) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class a.b.c.myapp1.beans.Preferences] with qualifiers [@Any @Default] at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:459) at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:125) at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:174) at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:325) at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:116) at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:217) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:358) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) ... 5 moreit mostly occurs on server (re-)starts.
in many cases this goes hand in hand with an second exception of an other deployment:
{25.03.2013 08:34:11,499 ERROR [ org.jboss.msc.service.fail] ([MSC service thread 1]) MSC00001: Failed to start service jboss.deployment.unit."myapp2.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."myapp2.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name preferences resolves to beans [Managed Bean [class a.b.c.myapp2.bean.Myapp2Preferences] with qualifiers [@Any @Default @Named], Managed Bean [class a.b.c.mylib.DefaultPreferences] with qualifiers [@Any @Default @Named]] at org.jboss.as.weld.services.WeldService.start(WeldService.java:83) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name preferences resolves to beans [Managed Bean [class a.b.c.myapp2.bean.Myapp2Preferences] with qualifiers [@Any @Default @Named], Managed Bean [class a.b.c.mylib.DefaultPreferences] with qualifiers [@Any @Default @Named]] at org.jboss.weld.bootstrap.Validator.validateBeanNames(Validator.java:476) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:373) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:380) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83) at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) ... 5 moreboth applications are using the same library (=bean archive) in their /WEB-INF/lib !
the bean archive contains an @javax.inject.Named("preferences") @javax.enterprise.context.SessionScoped class DefaultPreferences and the applications which are using this library provide their own @Specializes Preferences class.
it isn't really hard to reproduce the problem. you only have to shutdown/startup the container several times.