[
https://issues.jboss.org/browse/WFLY-5083?page=com.atlassian.jira.plugin....
]
Miroslav Novak moved JBEAP-660 to WFLY-5083:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-5083 (was: JBEAP-660)
Workflow: GIT Pull Request workflow (was: CDW v1)
Affects Version/s: (was: EAP 7.0.0.DR7)
Component/s: JMS
(was: JMS)
(was: Migration)
Target Release: (was: EAP 7.0.0.GA)
[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
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)