[jboss-jira] [JBoss JIRA] (WFLY-5083) [Migration operation] group-address/group-port/local-bind-address/local-bind-port in broadcast-group are not migrated

[Miroslav Novak (JIRA)]

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

Miroslav Novak updated WFLY-5083:
---------------------------------
    Affects Version/s: 10.0.0.Beta1


> [Migration operation] group-address/group-port/local-bind-address/local-bind-port in broadcast-group are not migrated
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-5083
>                 URL: https://issues.jboss.org/browse/WFLY-5083
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 10.0.0.Beta1
>            Reporter: Miroslav Novak
>            Assignee: Jeff Mesnil
>
> If broadcast group with local-bind-address,local-bind-port, group-address and group-port then those parameters are not migrated properly:
> For example HornetQ configuration:
> {code}
>  <broadcast-group name="groupA">
>                 <local-bind-address>localhost</local-bind-address>
>                 <local-bind-port>12345</local-bind-port>
>                 <group-address>224.0.1.105</group-address>
>                 <group-port>23456</group-port>
>                 <broadcast-period>${broadcast.period:2500}</broadcast-period>
>                 <connector-ref>netty</connector-ref>
>                 <connector-ref>netty-throughput</connector-ref>
>             </broadcast-group>
> {code}
> is migrated to Artemis like:
> {code}
>                 <broadcast-group name="groupA" connectors="netty netty-throughput" broadcast-period="${broadcast.period:2500}"/>
> {code}
> With such a configuration server cannot be started. There is no warning pointing to this problem.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)