Bug 1085243
| Summary: | org.jboss.msc.service.DuplicateServiceException: Service jboss.ra.deployment."org.jboss.genericjms" is already registered | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Miroslav Novak <mnovak> | ||||||
| Component: | JCA | Assignee: | Stefano Maestri <smaestri> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Simka <msimka> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.3.0 | CC: | jmesnil, kkhan, msvehla, ochaloup, smumford | ||||||
| Target Milestone: | ER2 | Keywords: | Regression, TestBlocker | ||||||
| Target Release: | EAP 6.3.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-06-28 15:42:38 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: | 1051640 | ||||||||
| Attachments: |
|
||||||||
Same configuration is working in EAP 6.3.0.DR6 without any problem. Created attachment 883930 [details]
standalone-full.xml
Created attachment 883931 [details]
server.log
I confirm this regression also occurs on WildFly and is caused by https://issues.jboss.org/browse/WFLY-2912. If I revert its commit, the generic JMS RA is deployed fine. EAP 6.3.0.ER2 can be started without problem. Thanks for the fix! Setting as verified. Marking for exclusion from 6.3.0 Beta release notes as both 'affects' and 'fix' versions are listed as 6.3.0, suggesting this was not a customer-facing issue. |
Description of problem: There is regression in EAP 6.3.0.ER1 which is test blocker for Tibco EMS certification. When generic resource adapter is configured for Tibco EMS 6.3. then it's registered twice. Server log shows ERROR: 17:32:16,763 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 48) JBAS014612: Operation ("add") failed - address: ([ ("subsystem" => "resource-adapters"), ("resource-adapter" => "org.jboss.genericjms") ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.ra.deployment."org.jboss.genericjms" is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:236) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:742) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:243) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2433) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:345) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1442) [jboss-as-controller-7.4.0.Final-redhat-8.jar:7.4.0.Final-redhat-8] at org.jboss.as.connector.util.RaServicesFactory.createDeploymentService(RaServicesFactory.java:104) at org.jboss.as.connector.subsystems.resourceadapters.RaOperationUtil.activate(RaOperationUtil.java:312) at org.jboss.as.connector.subsystems.resourceadapters.RaAdd$1.execute(RaAdd.java:94) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:601) [jboss-as-controller-7.4.0.Final-redhat-8.jar:7.4.0.Final-redhat-8] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:479) [jboss-as-controller-7.4.0.Final-redhat-8.jar:7.4.0.Final-redhat-8] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:283) [jboss-as-controller-7.4.0.Final-redhat-8.jar:7.4.0.Final-redhat-8] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:278) [jboss-as-controller-7.4.0.Final-redhat-8.jar:7.4.0.Final-redhat-8] In standalone-full.xml is configured only one resource adapter: <subsystem xmlns="urn:jboss:domain:resource-adapters:1.1"> <resource-adapters> <resource-adapter id="org.jboss.genericjms"> <module slot="main" id="com.tibco.tibjms"/> <transaction-support>NoTransaction</transaction-support> <connection-definitions> <connection-definition class-name="org.jboss.resource.adapter.jms.JmsManagedConnectionFactory" jndi-name="java:/jms/CF" pool-name="CF"> <config-property name="JndiParameters"> java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory;java.naming.provider.url=tcp://<tibco-server>:7222 </config-property> <config-property name="ConnectionFactory"> CF </config-property> <security> <application/> </security> </connection-definition> </connection-definitions> </resource-adapter> </resource-adapters> </subsystem>