[
https://issues.jboss.org/browse/WFLY-5083?page=com.atlassian.jira.plugin....
]
Kabir Khan updated WFLY-5083:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many
of these so I am not checking the history properly. From the lastModified date of this
issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc.
for this exercise). If that is incorrect please adjust as needed.
[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
Fix For: 10.0.0.Final
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
(v7.5.0#75005)