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 > network but not with a broker on the other side of a firewall. Can anyone > confirm that they are communicating through a firewall having opened only > TCP 61616? > -- View this message in context: http://old.nabble.com/Firewall%2C-is-TCP-61616-sufficient--tp25857741p26421334.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
