[jboss-jira] [JBoss JIRA] (AS7-1931) Unable to configure more than one pooled-connection-factory in the messaging subsystem

[Brian Stansberry (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/AS7-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated AS7-1931:
----------------------------------

           Assignee: Andy Taylor
      Fix Version/s: 7.1.0.CR1
        Component/s: JMS
    Forum Reference: http://community.jboss.org/thread/172692  (was: http://community.jboss.org/thread/172692)

    
> Unable to configure more than one pooled-connection-factory in the messaging subsystem
> --------------------------------------------------------------------------------------
>
>                 Key: AS7-1931
>                 URL: https://issues.jboss.org/browse/AS7-1931
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 7.0.0.Final, 7.0.1.Final, 7.0.2.Final
>         Environment: Windows7, sun jdk 1.6_25
>            Reporter: Vincent MATHON
>            Assignee: Andy Taylor
>             Fix For: 7.1.0.CR1
>
>
> Adding another pooled connection factory in the standalone-preview.xml file provided by any of the 7.0.x.Final releases as follow
>               <pooled-connection-factory name="hornetq-ra">
>                  <transaction mode="xa"/>
>                  <connectors>
>                     <connector-ref connector-name="in-vm"/>
>                  </connectors>
>                  <entries>
>                     <entry name="java:/JmsXA"/>
>                  </entries>
>               </pooled-connection-factory>
>               <pooled-connection-factory name="hornetq-ra-nonxa">
>                  <transaction mode="local"/>
>                  <connectors>
>                     <connector-ref connector-name="in-vm"/>
>                  </connectors>
>                  <entries>
>                     <entry name="java:/JmsNonXA"/>
>                  </entries>
>               </pooled-connection-factory>
> leads to the following exception:
> 12:44:31,621 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.messaging.pooled-connection-factory.hornetq-ra-nonxa: org.jboss.msc.service.StartException in service jboss.messaging.pooled-connection-factory.hornetq-ra-nonxa: failed to create resource adapter
> 	at org.jboss.as.messaging.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:174)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25]
> 	at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.raactivator is already registered
> 	at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154)
> 	at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226)
> 	at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560)
> 	at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201)
> 	at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211)
> 	at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
> 	at org.jboss.as.messaging.jms.PooledConnectionFactoryService.createService(PooledConnectionFactoryService.java:232)
> 	at org.jboss.as.messaging.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:172)
> 	... 5 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira