This problem eventually went away by setting pubSubDomain to true in the
Spring JMS Template config,
but why this behaved differently in the presence of a firewall remains a
mystery.
wytten wrote:
>
> still haven't resolved this issue--I can communicate with a broker on my
> n
wytten wrote:
>
> Is there some other port which needs to be opened in addition to TCP
> 61616? I'm talking about the simplest case of using a single broker
> configuration.
>
I still haven't resolved this issue--I can communicate with a broker on my
network but
I've got a very simple Java/Spring program that works with an out-of-the-box
ActiveMQ 5.2.0 configuration when the broker is local. When I send a
message to the broker, I can see with the admin interface that the queue was
created and the message was received.
However, this same client program a
