Bug 1050963
| Summary: | [GSS] (6.3) Permanent fix for: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Adam Kovari <akovari> | ||||
| Component: | CDI/Weld | Assignee: | Jozef Hartinger <jharting> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Marek Schmidt <maschmid> | ||||
| Severity: | unspecified | Docs Contact: | Russell Dickenson <rdickens> | ||||
| Priority: | unspecified | ||||||
| Version: | 6.0.1 | CC: | bmaxwell, jharting, jwankhed, kkhan, lcosti, myarboro, nobody, pmuir, wfink | ||||
| Target Milestone: | DR0 | ||||||
| Target Release: | EAP 6.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Bean name ambiguity validation was not isolated in deployments with multiple sub-deployments, and this caused `DeploymentException` in some scenarios. This has been resolved with an upgrade of the Weld component in this release of Red Hat JBoss EAP 6.
|
Story Points: | --- | ||||
| Clone Of: | 1050959 | ||||||
| : | 1052277 (view as bug list) | Environment: | |||||
| Last Closed: | 2014-06-28 15:43:20 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1051638, 1052277 | ||||||
| Attachments: |
|
||||||
|
Description
Adam Kovari
2014-01-09 12:43:47 UTC
Created attachment 847646 [details]
Reproducer (maven) project
I test the project with EAP6.2.0 with the same result.
14:19:14,822 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-13) MSC000001: Failed to start service jboss.deployment.unit."twoWarProject.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."twoWarProject.ear".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name echo resolves to beans [Managed Bean [class org.jboss.tools.s2.EchoS2] with qualifiers [@Any @Default @Named], Managed Bean [class org.jboss.tools.s1.EchoS1] with qualifiers [@Any @Default @Named]]
at org.jboss.weld.bootstrap.Validator.validateBeanNames(Validator.java:480)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:374)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:379)
at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:64)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
... 3 more
14:19:15,032 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "twoWarProject.ear" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"twoWarProject.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"twoWarProject.ear\".WeldStartService: Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name echo resolves to beans [Managed Bean [class org.jboss.tools.s2.EchoS2] with qualifiers [@Any @Default @Named], Managed Bean [class org.jboss.tools.s1.EchoS1] with qualifiers [@Any @Default @Named]]"}}
Fixed upstream. The fix will be available in Weld 1.1.17.Final Marek Schmidt <maschmid> updated the status of jira WELD-1584 to Reopened Jozef Hartinger <jharting> updated the status of jira WELD-1584 to Resolved Setting to ON_QA since upgrade should fix this Verified on EAP 6.3.0.ER1 |