Enterprise Integration Zone is brought to you in partnership with:

Bosanac Dejan is a Senior Software Engineer at FuseSource specializing in messaging and integration with Apache ActiveMQ Dejan is a DZone MVB and is not an employee of DZone and has posted 16 posts at DZone. You can read more from them at their website. View Full User Profile

Apache ActiveMQ 5.7.0 Released! Adds Java 7 Compatibility

10.08.2012
| 5973 views |
  • submit to reddit

We managed to keep our goal of making more frequent releases and today we’re happy to announce Apache ActiveMQ 5.7.0. The main goal of this release was Java 7 compatibility. The project is built using JDK 6, but it’s tested to work properly with Java 7. This was needed as we now use Camel 2.10, which also added support for Java 7.

Besides this, there’s a couple of new features and close to two hundred bug fixes in this release. Some of the prominent new features are:

  • Secure WebSocket (wss) transport – which means that you can now securely connect to the broker directly from your browser. You can find more information about it here

  • Broker Redelivery – which allows you to define redelivery policy such that broker will resend a message to a different consumer in case that processing fails. Here you can find more information on when you’d want to use this feature and how.

We also improved our storage locking mechanism, so now it’s completely pluggable. This means that locking is not tied to the store itself, but it’s separately configured. And also you can tune it or implement new locking strategies to suit your environment. We also provided a new database locker, called Lease Database Locker, which should do much better job for JDBC master slave scenarios.

So, that’s about it. Give 5.7.0 a try and let us know what do you want to see in 5.8.0.

And while I have your attention, there’re two upcoming sessions where you can learn more about ActiveMQ:

Published at DZone with permission of Dejan Bosanac, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)