activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wytten <>
Subject Firewall, is TCP 61616 sufficient?
Date Mon, 12 Oct 2009 15:29:27 GMT

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 appears to block-on-send when the broker
is behind a firewall.
Opening TCP 61616 on the firewall allowed me to connect to the broker.
Using the admin interface, I can see that the queue is created, however no
message is received and the client blocks during send.

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.

ActiveMQ 5.2.0, Java 1.5, Spring 2.5.6


  public void say(final String message) {
    this.jmsTemplate.send(new MessageCreator() {

      public Message createMessage(Session session) throws JMSException {
        ObjectMessage object = session.createObjectMessage();
        return object;



View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message