What’s new in Apache ActiveMQ 5.4.0

Apache ActiveMQ 5.4.0 is out. Beside our usual dedication to making it bullet-proof by adding a lot of test cases and resolving issues reported by our vibrant community, this release contains a lot of new features (some of which has already been covered here). In this post I’ll try to sum up the new features that we included in this release. As the development pace was very rapid, some of them haven’t been documented yet, but that’ll change soon too. So let’s start:

These are definitely interesting times for open source messaging and be sure to expect a lot more from ActiveMQ team (such as new Apollo architecture). Also, don’t miss Rob Davies talking on Deploying ActiveMQ in the Enterprise on August 19th.

2 Responses to “What’s new in Apache ActiveMQ 5.4.0”

  • Kshitiz

    Hi,

    Thanks for your useful blog!

    I am aiming to create a notification server (a pub/sub and p2p model) and excited to use Spring Integration’s features. To make that notification server an isolated black box, I m thinking to expose its functionality thru rest based APIs. Since ActiveMQ is highly configurable so probably going to use it for the message management part.

    Do You think that it’s a feasible & a wise decision to go for an architecture like this considering scalability & extensibility ?

    External systems Restful APIs on Tomcat Spring Integration acting as lightweight ESB ActiveMQ (+MySql for message persistence and tomcat i.e. not the ‘embedded’ jetty) Spring Integration Restful APIs External systems

    What all pros & cons do you suggest in this scenario…..

    Many thanks,
    Kshitiz

    Reply
  • Dejan Bosanac

    Hi Kshitiz,

    i think your architecture proposal looks fine. Just a couple of things you can consider:

    • using Apache Camel (http://camel.apache.org/) for an integration part as it is much better integrated with ActiveMQ
    • using default ActiveMQ KahaDB store instead of MySQL (you’ll have one app less to administer)

    Good luck with your project!

    Reply
  • Leave a Reply