Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5083

[Migration operation] group-address/group-port/local-bind-address/local-bind-port in broadcast-group are not migrated

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 10.0.0.Beta1
    • Fix Version/s: 10.0.0.Final
    • Component/s: JMS
    • Labels:
      None

      Description

      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:

       <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>
      

      is migrated to Artemis like:

                      <broadcast-group name="groupA" connectors="netty netty-throughput" broadcast-period="${broadcast.period:2500}"/>
      

      With such a configuration server cannot be started. There is no warning pointing to this problem.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jmesnil Jeff Mesnil
                  Reporter:
                  mnovak Miroslav Novak
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: