Installing Apache Active MQ on Ubuntu
After creating a Sales Demonstration system for an industry trade show using Ubuntu 10.10, I decided to create a personal development system based on one of my personal favorite free operating systems, Ubuntu. An old laptop was pressed into service as a meager server on which I could refresh my admin skills and provide a target for testing prototype concepts rambling around my brain. One of the first services this little laptop will host is Apache Active MQ 5.4.2 which was released December of 2010. (Authors Note: This article has been updated to support Ubuntu 11 and ActiveMQ 5.5)
Although Ubuntu has a large collection of software available in many repositories, there is no way, currently, to perform an
Move it to
The
Some (many?, most?) systems will give a system user a false login shell. This will keep the
Go to the end of the list of accounts and make sure the shell for this account looks something like the following line. Don't worry about the numbers and such, but make sure the last argument contains
Recursively change the ownership of the entire
Next, sym-link the init script provided by Active MQ to
Tell Ubuntu to start Active MQ on boot:
At this point you will probably get a warning about missing LSB information. LSB information is a block of information which directs how the links are made. See http://wiki.debian.org/LSBInitScripts for more details.
Now, let's build a default configuration file:
Change the owner and group of the config file:
Change the file permissions so its read-write by root only:
Unfortunately, this is where you will have to begin searching through your configuration file and make changes specific to your version of software and setup. There have been some changes between releases of Active MQ so the instructions may not match what you see in your files.
Edit the newly generated
You're looking for
Now we will configure the Active MQ broker to listen for JMX connections. Further down the file, un-comment the JMX configuration lines:
The above configuration lines enable JMX on port 11099 and use two file to control access through JMX.
The next section will specify how the shutdown script will connect to the broker (via JMX) and log into the management console to issue the shutdown command. This line will connect to broker via port 11099 and log in as
Save your changes to the configuration file and exit the editor.
Now, you must edit the
Ensure that these JMX access control files are readable by only the
Doing that enables the init script to connect to the locally running software via JMX, a management console. Without this configured correctly you're looking at issuing a shutdown command and seeing a ton of Java errors followed by thirty seconds (configurable) of timeout before the script finally issues a
Now run the service
Then look in the
Although Ubuntu has a large collection of software available in many repositories, there is no way, currently, to perform an
apt-get
for Active MQ. It has to be installed by hand. Fortunately, this is a relatively simple matter. There are a couple of stumbling blocks which prevented a smooth install for me so I thought this article might help others avoid them.Ensure you have Java installed
I prefer to have have thesun-java6-bin
and sun-java6-jre
packages for this purpose. I'm currently testing the free versions which come with Ubuntu. I have a separate link which describes installing sun-java on Ubuntu. It's like 5 commands; no big deal.Initial Install
Go to the download page for Apache Active MQ and select the latest available release tarball and extract it on your server.tar xzf apache-activemq-5.5.0-bin.tar.gz
Move it to
/opt
where optional software package are intended to be placed.sudo mv apache-activemq-5.5.0 /opt
The
activemq
scripts expect to find Active MQ installed in /opt/activemq
. I personally do not like having a non-versioned directory like that. Moving the package to /opt/activemq
as would be expected by the scripts can make it difficult months down the line to upgrade. What version is installed? Will you remember? Now, this is a personal preference, but I like to know at any time what versions of software I have installed so I generally create a sym-link so the script finds things where it expects and I can see what version is installed. It is also easier to switch versions by simply linking /opt/activemq
to another directory containing a different version. If it works fine, I can delete the old version, if not, I can switch the like back all this happens without changing any of the scripts. Here is how I did it:sudo ln -sf /opt/apache-activemq-5.5.0/ /opt/activemq
Add Non-Privileged Account
It's never a good idea to run a service as root, so it is a common practice to add a dedicated user account which doesn't have much authority and run the service as this account. This will have the added benefit of making the process easier to identify with tools such asps
and top
.sudo adduser -system activemq
Some (many?, most?) systems will give a system user a false login shell. This will keep the
activemq
script from running so you will have to make sure the account uses the bash
shell. First, open the /etc/passwd
file in your favorite editor. Don't forget to use sudo
as it is a privileged file. Here is the line when using vi
:sudo vi /etc/passwd
Go to the end of the list of accounts and make sure the shell for this account looks something like the following line. Don't worry about the numbers and such, but make sure the last argument contains
/bin/bash
and not something like /bin/false
, for example, the line should look something like the following:activemq:x:116:65534::/home/activemq:/bin/bash
Recursively change the ownership of the entire
activemq
directory to the activemq
user you just added.sudo chown -R activemq: /opt/apache-activemq-5.5.0/
Next, sym-link the init script provided by Active MQ to
/etc/init.d/activemq
:sudo ln -sf /opt/activemq/bin/activemq /etc/init.d/
Tell Ubuntu to start Active MQ on boot:
sudo update-rc.d activemq defaults
At this point you will probably get a warning about missing LSB information. LSB information is a block of information which directs how the links are made. See http://wiki.debian.org/LSBInitScripts for more details.
Now, let's build a default configuration file:
sudo /etc/init.d/activemq setup /etc/default/activemq
Change the owner and group of the config file:
sudo chown root:nogroup /etc/default/activemq
Change the file permissions so its read-write by root only:
sudo chmod 600 /etc/default/activemq
Editing the Configuration
Unfortunately, this is where you will have to begin searching through your configuration file and make changes specific to your version of software and setup. There have been some changes between releases of Active MQ so the instructions may not match what you see in your files.
Edit the newly generated
/etc/default/activemq
file. I'll use vi
:sudo vi /etc/default/activemq
You're looking for
ACTIVEMQ_USER=""
. Enter the name of your activemq
user name between the quotes.Now we will configure the Active MQ broker to listen for JMX connections. Further down the file, un-comment the JMX configuration lines:
ACTIVEMQ_SUNJMX_START="-Dcom.sun.management.jmxremote.port=11099 "
ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_CONFIG_DIR}/jmx.password"
ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_CONFIG_DIR}/jmx.access"
ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.ssl=false"
ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote"
ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_CONFIG_DIR}/jmx.password"
ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_CONFIG_DIR}/jmx.access"
ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote.ssl=false"
ACTIVEMQ_SUNJMX_START="$ACTIVEMQ_SUNJMX_START -Dcom.sun.management.jmxremote"
The above configuration lines enable JMX on port 11099 and use two file to control access through JMX.
The next section will specify how the shutdown script will connect to the broker (via JMX) and log into the management console to issue the shutdown command. This line will connect to broker via port 11099 and log in as
controlRole
with a password of abcd1234
. Keep these values (or whatever you change them to) in mind as you will need to make sure they are registered in the data/jmx.password
and data/jmx.access
files in the next steps.ACTIVEMQ_SUNJMX_CONTROL="--jmxurl service:jmx:rmi:///jndi/rmi://127.0.0.1:11099/jmxrmi --jmxuser controlRole --jmxpassword abcd1234"
# ACTIVEMQ_SUNJMX_CONTROL=""
# Specify the queue manager URL for using "browse" option of sysv initscript
ACTIVEMQ_QUEUEMANAGERURL="--amqurl tcp://localhost:61616"
# ACTIVEMQ_SUNJMX_CONTROL=""
# Specify the queue manager URL for using "browse" option of sysv initscript
ACTIVEMQ_QUEUEMANAGERURL="--amqurl tcp://localhost:61616"
Save your changes to the configuration file and exit the editor.
Now, you must edit the
conf/jmx.password
and conf/jmx.access
files. Use the sample data they provide in the comments immediately above the lines. Remember to use the values you specified (or left alone) int the --jmxuser
and --jmxpassword
of the ACTIVEMQ_SUNJMX_CONTROL
configuration line above.Ensure that these JMX access control files are readable by only the
activemq
user account!sudo chmod 600 /opt/apache-activemq-5.5.0/conf/jmx.password
sudo chmod 600 /opt/apache-activemq-5.5.0/conf/jmx.access
sudo chmod 600 /opt/apache-activemq-5.5.0/conf/jmx.access
Doing that enables the init script to connect to the locally running software via JMX, a management console. Without this configured correctly you're looking at issuing a shutdown command and seeing a ton of Java errors followed by thirty seconds (configurable) of timeout before the script finally issues a
KILL
on the process. Now run the service
sudo /etc/init.d/activemq start
Then look in the
/opt/activemq/data
directory for the PID and log files. You can tail
the log file to see what is happening:sudo tail -f /opt/activemq/data/activemq.log
All Done!
The Active MQ broker should be running. You can test this in a variety of ways including using thetelnet
command to connect to the broker on 61616, the JMX port on 11099 or more simply by opening a browser connection to the HTTP management port: http://localhost:8161
22 comments:
I know you're not using the apt package but still thank a lot!
ACTIVEMQ_SUNJMX_CONTROL="--jmxurl service:jmx:rmi:///jndi/rmi://127.0.0.1:11099/jmxrmi --jmxuser control --jmxpassword abcd1234"
# ACTIVEMQ_SUNJMX_CONTROL=""
# Specify the queue manager URL for using "browse" option of sysv initscript
ACTIVEMQ_QUEUEMANAGERURL="--amqurl tcp://localhost:61616"
A tip for others who wanted to move the ACTIVEMQ_DATA directory (I wanted to put mine in /var/local/activemq): The log files assume that it is ACTIVEMQ_BASE/data, which caused errors on startup because that directory did not exist. I had to make some changes to $ACTIVEMQ_BASE/conf/log4j.properties to get it to work:
log4j.appender.logfile.file=${activemq.data}/activemq.log
log4j.appender.audit.file=${activemq.data}/audit.log
Where /etc/hostname contains 'foo' your /etc/hosts file must map 'foo' to an IP in the 127.x.x.x range.
127.0.0.1 localhost
127.0.1.1 foo
I have been following http://activemq.apache.org/encrypted-passwords.html in order to encrypt my configuration passwords, but I could not figure it out where in the init or configuration stript I should set the loading.
I tried setting the variable COMMANDLINE_ARGS="$@ xbean:../conf/activemq-security.xml" without success
tks.
There was no problem during installation :)
I got the following stacktrace when stopping activemq...
ERROR: java.lang.IllegalArgumentException: JMX URL already specified.
java.lang.IllegalArgumentException: JMX URL already specified.
at org.apache.activemq.console.command.AbstractJmxCommand.handleOption(AbstractJmxCommand.java:349)
at org.apache.activemq.console.command.ShutdownCommand.handleOption(ShutdownCommand.java:165)
at org.apache.activemq.console.command.AbstractCommand.parseOptions(AbstractCommand.java:73)
at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:45)
at org.apache.activemq.console.command.AbstractJmxCommand.execute(AbstractJmxCommand.java:387)
at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:150)
at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.activemq.console.Main.runTaskClass(Main.java:262)
at org.apache.activemq.console.Main.main(Main.java:115)
Stopping broker: localhost
.. FINISHED
Could you help me?
How to resolve it?
It saved me struggling up for days.
sudo /etc/init.d/activemq stop
This gives an error. Any command?
Post a Comment