activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: TCP connection to broker from behind NAT
Date Fri, 04 Mar 2011 17:08:22 GMT
can you get request reply to work with a local broker?

There are two ports involved, the client port (usually dynamically
assigned, and the server or broker port (66167). You may have to open
up the client port on your firewall to allow packets from the broker
to get through to the client.

a client side broker url of the form: tcp://xxx:61610/xxx:61617 will
restrict the client side to port 61610 when it connects to 61617

http://activemq.apache.org/how-do-i-define-a-local-address-and-local-port-for-tcp-or-ssl.html

On 3 March 2011 22:15, Bryan <bryanck@gmail.com> wrote:
> One other thing I noticed. When I do not try to establish a reply queue, I do
> not see any messages about advisory queues being initialized. When I do
> create a temporary reply queue, however, I see messages about advisory
> queues, e.g. adding destination: topic://ActiveMQ.Advisory.TempQueue.
> Perhaps my issue is somehow related to advisory messages? I tried disabling
> advisory messages but this did not resolve my issue.
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/TCP-connection-to-broker-from-behind-NAT-tp3332715p3334329.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
http://blog.garytully.com
http://fusesource.com

Mime
View raw message