[jboss-as7-dev] make <socket-binding>'s port optional

[Kabir Khan]

On 20 Mar 2012, at 10:38, Jeff Mesnil wrote:

>> On 3/19/12 10:57 AM, Jeff Mesnil wrote:
>>> I am working on an issue in the domain model for HornetQ cluster
>>> configuration[1].
>>> To be configured properly, I want to specify only a multicast-address
>>> and multicast-port but not the local port (and let the OS open one).
> 
> 
> I fixed the code to use properly a socket-binding for HornetQ cluster 
> configuration.
> 
> Now, I want to be able to run separate clusters on the same network 
> (that's the original issue raised by QA ).
> I will do that by adding a property extension to the messaging-group's 
> multicast-address:
> 
> <socket-binding name="messaging-group" 
> multicast-address="${jboss.hornetq.cluster.address:231.7.7.7}" 
> multicast-port="9876"/>
> 
> 1) What's the convention for naming this property? 
> jboss.hornetq.cluster.address or jboss.messaging.group.address something 
> else?
I think jboss.messaging.group.address looks more the convention used already for the socket bindings
> 
> 2) At first, I wanted to run separate clusters using port offset. 
> However there is nothing similar for the multicast-port. Does that make 
> sense to add it or is it really specific to this HornetQ conf?

I think something specific makes it look too "complex" for your average user, so perhaps simply
> <socket-binding name="messaging-group" 
> multicast-address="${jboss.messaging.group.address:231.7.7.7}" 
> multicast-port="${jboss.messaging.group.port:9876}"/>


Then whatever starts the two clusters uses different values for the port for the two clusters?

> 
> 
> thanks,
> jeff
> 
> [1] https://issues.jboss.org/browse/JBPAPP-8178
> 
> -- 
> Jeff Mesnil
> JBoss, a division of Red Hat
> http://jmesnil.net/
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev