3 Replies Latest reply on Sep 7, 2012 2:15 PM by Clebert Suconic

    HQ 2.3.0.Alpha broker discovery configuration - broadcast port not opened?

    Michael Justin Novice

      I added the broadcast-groups, discovery-groups and cluster-connections sections in the standalone non-clustered configuration

      of HornetQ 2.3.0 Alpha as documented on http://docs.jboss.org/hornetq/2.3.0.Alpha/docs/user-manual/html/clusters.html

       

      Do I understand correctly that this would allow discovery of the brokers in the local network (using IP multicast)?

       

      My problem is that the port 9876 specified in the broadcast-groups and discovery-groups is not opened when the broker runs.

       

      Is this feature limited to clustered brokers or is there something else which needs to be configured?

       

      Many thanks in advance!

       

       

       


      <broadcast-groups>

      <broadcast-group name="bg-group1">

      <group-address>231.7.7.7</group-address>

      <group-port>9876</group-port>

      <broadcast-period>1000</broadcast-period>

      <connector-ref>netty-connector</connector-ref>

      </broadcast-group>

      </broadcast-groups>

       


      <discovery-groups>

      <discovery-group name="dg-group1">

      <group-address>231.7.7.7</group-address>

      <group-port>9876</group-port>

      <refresh-timeout>60000</refresh-timeout>

      </discovery-group>

      </discovery-groups>

       


      <cluster-connections>

      <cluster-connection name="my-cluster">

      <address>jms</address>

      <connector-ref>netty-connector</connector-ref>

      <discovery-group-ref discovery-group-name="dg-group1"/>

      <!--max hops defines how messages are redistributed, the default is 1 meaning only distribute to directly

      connected nodes, to disable set to 0-->

      <!--<max-hops>0</max-hops>-->

      </cluster-connection>

      </cluster-connections>