Apache ActiveMQ 5.2 is primarily a maintenance release which resolves
New Features in 5.2
The new features and enhancements in this release include:
- Additional advisory messages for messages delivered/consumed fast producers/slow consumers, Usage limits, Slaves become masters etc.
- Enhanced ssl context configuration through spring/xbean
- New individual acknowledge mode for message consumption
- Ability to configure the automatic discarding of the items being sent to the dead letter queue
- Ability to limit the maximum number of connections to a Broker
- Ability to configure separate lock Datasource for JDBC Master slave.
- activemq-camel and activemq-connection-pool now have their own modules, no longer in activemq-core
- The default ActiveMQConnectionFactory brokerUrl now uses the failover transport.
- Uses Apache Camel 1.5.
Getting the Binary Distributions
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:
- Download the KEYS
- Download the asc signature file for the relevant distribution
- Verify the signatures using the following commands, depending on your use of PGP or GPG:
(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
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:
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:
Getting the Source Code
SVN Tag Checkout
For a more detailed view of new features and bug fixes, see the release notes
Also see the previous ActiveMQ 5.1.0 Release