activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eraos <>
Subject Bind only to localhost/private network
Date Tue, 24 Aug 2010 21:47:07 GMT

Hi, I'm a new ActiveMQ user (ActiveMQ 5.4.0 on Ubuntu Lucid Lynx) and have
been trying to lock-down/secure an ActiveMQ instance for this entire
afternoon without really getting anywhere appreciable.  I was hoping someone
here could help me.

Specifically, what I want is for ActiveMQ to:

1) Bind all administrative and miscellaneous sockets to localhost.
2) Bind only the STOMP transport to a private network.

I've achieved #2, but #1 really elludes me badly.  The bindings of my
ActiveMQ server currently look like this, according to netstat:

Proto Recv-Q Send-Q Local Address           Foreign Address         State      
PID/Program name
tcp6       0      0     :::*                    LISTEN     
tcp6       0      0 :::33689                      :::*                   
LISTEN      5119/java
tcp6       0      0 :::11099                      :::*                   
LISTEN      5119/java
tcp6       0      0 :::11100                      :::*                   
LISTEN      5119/java

As you can see, the transport binding (port 61617) is correctly on the
private network; but the other three are wildcard bindings that I really
want turned into localhost bindings, but I cannot for the life of me figure
out how to do it.

The command-line that ActiveMQ is currently executed as is:

  -jar /opt/apache-activemq-5.4.0/bin/run.jar

... and my /etc/activemq.xml file looks like this (comments trimmed out):


        <property name="locations">
    <broker xmlns=""
brokerName="localhost" dataDirectory="${activemq.base}/data"
persistent="false" useJmx="true">
                <policyEntry topic=">" producerFlowControl="false">
                    <vmCursor />
                <policyEntry queue=">" producerFlowControl="false">
            <managementContext connectorPort="11099"
jmxDomainName="org.apache.activemq" rmiServerPort="11100"/>
            <kahaDB directory="${activemq.base}/data/kahadb"/>
            <transportConnector name="stomp"

I am reasonably certain that the "extra" ports (i.e. ports 33689, 11099, and
11100 in the above netstat output) are due to jmx/rmi but I cannot for the
life of me figure out how to secure them by forcing them to bind localhost
instead of binding to the wildcard address.  Can anyone point me in the
right direction as to how to achieve this, please?

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

View raw message