[jboss-jira] [JBoss JIRA] (WFLY-5380) [Migration operation] Do not create legacy connection factory for connection factories with in-vm connector

[Jeff Mesnil (JIRA)]

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

Jeff Mesnil moved JBEAP-1127 to WFLY-5380:
------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-5380  (was: JBEAP-1127)
             Workflow: GIT Pull Request workflow   (was: CDW v1)
          Component/s: JMS
                           (was: JMS)
                           (was: Migration)
       Target Release:   (was: 7.0.0.GA)
    Affects Version/s: 10.0.0.CR1
                           (was: 7.0.0.DR9)


> [Migration operation] Do not create legacy connection factory for connection factories with in-vm connector
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-5380
>                 URL: https://issues.jboss.org/browse/WFLY-5380
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 10.0.0.CR1
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>              Labels: Migration
>
> If connection factory contains in-vm connector and legacy connection factory is created by migration operation then server won't start and fails with:
> {code}
> 12:51:16,267 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.messaging-activemq.default.jms.connection-factory.legacy.InVmConnectionFactory: org.jboss.msc.service.StartException in service jboss.messaging-activemq.default.jms.connection-factory.legacy.InVmConnectionFactory: WFLYMSGAMQ0082: Unsupported type of connector factory for legacy resource: java.lang.String
> 	at org.wildfly.extension.messaging.activemq.jms.legacy.LegacyConnectionFactoryService.translateFactoryClassName(LegacyConnectionFactoryService.java:311)
> 	at org.wildfly.extension.messaging.activemq.jms.legacy.LegacyConnectionFactoryService.translateTransportGroupConfigurations(LegacyConnectionFactoryService.java:294)
> 	at org.wildfly.extension.messaging.activemq.jms.legacy.LegacyConnectionFactoryService.start(LegacyConnectionFactoryService.java:183)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]
> 	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]
> {code}
> Configuration of connection factory and in-vm connector:
> {code}
> <in-vm-connector name="in-vm" server-id="${my.server-id:0}"/>
> <legacy-connection-factory name="InVmConnectionFactory" connectors="in-vm" entries="${connection-factory.entries.entry:java:/ConnectionFactory}"/>
> {code}
> Problem seems to be that HornetQ connection factory does not accept Artemis InVMConnectorFactory class. 
> As legacy connection factories with in-vm connector cannot be used by standalone JMS client (not serializable) then there is no reason to create them by migration operation.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)