Open MQ


As with any forward view, these plans are subject to change without any notice. We strive to keep the community informed of our progress and plans however things do change from time to time. We'll do our best to let you know as the future becomes ever more clear. You're always welcome to send an inquiry to if you want the very latest.

Open MQ 4.3

This is the current stable release of Open MQ

  • Universal Message Client for Java MQ
  • Better AIX support
  • Windows 2008
  • Oracle 11g

This release was finalized in December, 2008. It was included as the JMS provider in GlassFish v2.1.

For more details, downloads, and updates about this release, you can read about it at the Open MQ 4.3 description page.

Open MQ 4.4

This is the focus of our current development efforts. This release will be specifically aimed at changes required for supporting GlassFish v3. There are some changes in the plans to support the new lifecycle requirements of Java EE 6 (in development as of Sept. 2008). The features proposed for this release are

  • JMS Bridge -- Connect to other Open MQ clusters, or other JMS products
  • STOMP -- use the Streaming Text Oriented Message Protocol in Open MQ
  • Embedding -- Use Open MQ as an embedded messaging provider in your own Java application

We're also looking at things we can do to improve performance. Our slant is toward improvements when using Open MQ in GlassFish v3, but the nature of this work is often that performance improvements make all Open MQ use better.

One late addition to this project is the introduction of a Visual VM monitoring plug in for Open MQ. We're still working to improve this and it's not clear we can complete this on our current finalization schedule.

You can read about this as well as other changes in progress, at the MQ 4.4 development page

Check the GlassFish v3 planning page for the most up to date timing details available. As of July., this is planned for late in the third quarter of 2009 (about September, 2009).

On the horizon

We are starting to put a plan together for the release following MQ 4.5. We're always interested to hear your opinion about what's important and what's not. If you have a suggestion, do post a note to

Some features that we think might make the cut for this release include:

  • Continued enhancements for integration with GlassFish 3
    • GlassFish Server Open Source Edition 3.1 Cluster support
    • Alignment with the JMSJCA RA project
  • Finalization of the VisualVM plug in for Open MQ (if this doesn't finish up in MQ 4.4)
  • Message level journaling and replay
  • Enhancements for JMS Bridge -- Forwarding based on selectors, subscription routing

We published some of what we were thinking about in our JavaOne Birds of a Feather (BOF) presentation. Here is a list, taken from that presentation (and extended a bit)

We are looking at the following enhancements for subsequent releases

  • Adding more options for High Availability. Ideas that we have discussed include
    • Better integration with MySQL
    • Writing our own replication and reliability infrastructure
    • Integrating with the Shoal project for message broker node discovery, status monitoring, and maybe more.
  • XML Interfaces (This is introduced in in MQ 4.3)
    • Integration with Google Web Toolkit (We opted not to go this route.)
    • XML (Rest style) interface for Broker to Broker communication (Internal Wire Protocol)
  • Other APIs
    • PHP Integration (We'd like feedback about our Web Integration in 4.3)
    • .NET / MSMQ integration (ibid for php)
    • Spring (Some users already support success with Spring.)
  • Journaling
    • To improve reliable write performance
    • To keep a transaction log, which may be replayed in case of failure
  • Store and Forward Messaging (Wide Area Network of Clusters)
  • JMS Destination Synchronization
  • Message encryption on-disk
  • Better administration integration with GlassFish Server Open Source Edition (This is being considered for GlassFish v3, i.e. MQ 4.4 or later)
    • Revised and extended administration console
  • Scalable in-memory destinations -- Allow messages to be spooled to disk, if memory limits are approached.
  • Performance improvements for specific use cases
  • General performance improvements
  • JMS specification improvements (would likely be handled under the JMS or Java EE specification)

Older Releases

Open MQ 4.2

This is the current production release of MQ. We are currently working on this release -- it is available as a Beta release as of June, 2008. This release is planned for release in July, 2008. This release is available now from the Downloads page.

Features added in this release included:

  • Wildcard destinations
  • XML Schema Validation
  • Registration support
  • MySQL support
  • C-API for XA -- Tested with Tuxedo Transaction Manager
  • Performance improvements

For more details on these features, as well as other updates, you can read the release notes for MQ 4.2

Open MQ 4.1

This release introduced the JDBC High Availability and Takeover feature. We also introduced the JMX interface in this release. This release is available now on the downloads page.


Is there a feature you want, but don't see here? Drop us a line ( and we'll add it to the list. If it gets too interactive, we'll move this over to the wiki.

Terms of Use; Privacy Policy; Copyright ©2013-2017 (revision 20160708.bf2ac18)
Please Confirm