activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raúl Kripalani <r...@evosent.com>
Subject Re: Best protocol & network interface binding
Date Wed, 06 Mar 2013 00:52:09 GMT
I assume you are talking about setting up a transportConnector on the broker side.
If so, just use the IP assigned to the network adapter as the hostname in the URI.

For example, if you have 3 network adapters:

en0, with IP 192.168.1.34
en1, with IP 172.16.4.2
en2, with IP 10.65.32.1

and you want the broker to listen on adapter en2 with OpenWire over TCP, you use the following
transportConnector configuration:

<transportConnector uri="tcp://10.65.32.1:<portNumber>?<options>" />

You can also use hostnames or FQDNs as far as I know.

Is this what you're after?

Regards,
Raúl.

On Mar 4, 2013, at 15:20, jan wrote:

> Can anybody help me with the network-interface binding? Is it so weird that I
> try to bind my message-listener to a certain network-interface? When true,
> how can/should I do it?
> 
> greetings
> Jan
> 
> 
> 
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Best-protocol-network-interface-binding-tp4664240p4664350.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message