Skip to main content

Setup Apache ActiveMQ

This is a follow up of my previous post JMS Cache Channel Setup. The goal is to configure JMS cache invalidation for Tridion Content Delivery. In my previous post I was describing how to configure the Tridion Deployer to use JMS technology and to post cache notification messages to an Apache ActiveMQ server. This post describes the steps I took to install and configure ActiveMQ on my machine.

I started my endeavor without having any prior experience with ActiveMQ. To my surprise, the installation was a breeze and took me about 20 minutes to get everything running.

I started by visiting the home of ActiveMQ -- The latest version as of the day was 5.10.0. I followed the no-nonsense guide on the home page and I first downloaded ActiveMQ. I use a Mac (like every freelancer who respects himself :-p) and I personally love FreeBSD, so I downloaded the Unix/Linux/Cygwin Distribution. Namely, a file named apache-activemq-5.10.0-bin.tar.gz.

The Getting Started Guide instructs you to:
  • decompress the archive to a folder of your choice (I used /srv). Execute the command
        tar zxvf activemq-5.10.0-bin.tar.gz

This creates folder /srv/apache-activemq-5.10.0
  • if activemq start-up script is not executable, make it executable by executing the following:
        > cd /srv/apache-activemq-5.10.0/bin
        > chmod 755 activemq

Next, you can proceed to configure ActiveMQ. This is where the Getting Started Guide is a bit inaccurate. Before being able to run ActiveMQ, you need to run the 'setup' command. This will create a configuration file in the location of your choice. I used my homedir ~/.activemqrc and executed the following:

        > cd /srv/apache-activemq-5.10.0
        > bin/activemq setup ~/.activemqrc

And really that's all, folks. You should now be able to run ActiveMQ, start up your Deployer and see it connect to the JMS server (check the cd_core log in debug mode).

Start command:

        > bin/activemq start

Shutdown command:

        > bin/activemq stop

Check running state:

        > bin/activemq status

Don't forget there is also a web console with default user & pass admin/admin, and it's very helpful in monitoring the server:



Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: I stumbled upon the following post from 2008 (!!!), , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven