New Features in 5.1

In the 5.1.x release of Apache ActiveMQ there are the following new features:

• You can use the new DestinationSource on an ActiveMQConnection to access the available queues or topics or listen to queues/topics being created or deleted.

  New Features in 5.1

• Support for more graceful handling of timeouts within MessageProducer.send
• Add the option for a backup channel that is already connected for the Failover transport
• ActiveMQ configuration can now validate against an XSD which means that it can be embedded in a spring configuration file.
• Stomp can now handle delivering Map and Object messages.

Getting the Binary Distributions

Do not use Safari to download, the above URLs use redirection The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox

Verify the Integrity of Downloads

It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:

1. Download the KEYS
2. Download the asc signature file for the relevant distribution
3. Verify the signatures using the following commands, depending on your use of PGP or GPG:

   $ pgpk -a KEYS
   $ pgpv apache-activemq-<version>-bin.tar.gz.asc
   

   or

   $ pgp -ka KEYS
   $ pgp apache-activemq-<version>-bin.tar.gz.asc
   

   or

   $ gpg --import KEYS
   $ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
   

(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).

Alternatively, you can verify the MD5 signature on the files. A Unix program called md5 or md5sum is included in most Linux and Unix distributions. It is also available as part of GNU Textutils. Windows users can utilize any of the following md5 programs:

• md5
• md5sums
• SlavaSoft FSUM

Error When Expanding Tarballs When expanding the binary tarballs you might wind up experiencing the following: $ tar zxvf /path/to/apache-activemq-5.1.0-bin.tar.gz apache-activemq-5.1.0/bin/run.jar apache-activemq-5.1.0/activemq-all-5.1.0.jar ... apache-activemq-5.1.0/webapps/fileserver/WEB-INF/web.xml apache-activemq-5.1.0/webapps/fileserver/WEB-INF/classes/org/apache/activemq/util/FilenameGuardFilter.class apache-activemq-5.1.0/webapps/fileserver/WEB-INF/classes/org/apache/activemq/util/FilenameGuardFilter$GuardedHttpServletRequest.class apache-activemq-5.1.0/webapps/fileserver/WEB-INF/classes/org/apache/activemq/util/RestFilter.class tar: Unexpected EOF in archive tar: A lone zero block at 61740 tar: Error exit delayed from previous errors These errors are a product of an open bug in Maven and are innocuous and won't affect anything.

Getting the Binaries using Maven 2

To use this release in your maven project, the proper dependency configuration that you should use in your Maven POM is:

<dependency>
  <groupId>org.apache.activemq</groupId>
  <artifactId>activemq-core</artifactId>
  <version>5.1.0</version>
</dependency>