Apache ActiveMQ 5.3.1 has just been released. It’s primarily the maintenance release, including nearly 100 bug fixes and improvements over the previous 5.3.0 version. The full list of improvements and bug fixes, as well as the download link, can be found at the release page.
- JDBC message store – a big effort has been made to make JDBC store as reliable as other file-based stores for use in complex high-load use cases.
stomp+niotransports – initial implementation of
stomp+niotransport, introduced in 5.3.0 version contained some resource leaks, but also revealed some problems with the
niotransport. All these are now fixed, thoroughly tested and ready for production use
- OSGi integration – a lot of small improvements in this area should provide much better integration of the broker in OSGi environments. Especially, we provided resources for seamless deployment in Apache Karaf OSGi runtime. This will be the topic of the following blog post (so stay tuned!)
- Web console security – Web console is now secured against XSS and XSRF attacks, so it’s safe to be deployed publicly (of course with proper authentication set in place)
Enjoy this release, while we work on delivering 5.4.0 in coming months (or even weeks) with more bug fixes and features, such as scheduled messages and web socket support
For the scheduled messages feature of 5.4.0, are the messages created by the broker or the producer? I’d think would need to be the broker if wanted to guarantee message delivery. I’m guessing is the broker since the web console supports cancellation of the jobs and such, but just want to be sure. Thanks
Messages are created by producers, just like regular messages. It’s just that delivery of those messages are delayed by the broker.
This seems similar to using the Delayer pattern with Camel then. Except you gain the precision of CRON scheduling… Would NMS be able to take advantage of this?
Yeah … You should just set appropriate headers
Comments are closed.