the end of 4.1 ...
By lindaschneider on Aug 08, 2007
This week is a pretty cool on for MQ because we just did what is hopefully out last build of 4.1 - our latest release and the release were we finally provide some sort of solution for High Availability (specifically data availability - we provided service availability in the past)
Its been a long few weeks cleaning up the last of the known high priority bugs and going through the lower priority ones to make sure nothing was missed.
Now everything is quiet.
I'll try to talk about HA a little more this week (how it works, why we did it that way) but for now my mind is on the future - what happens next.
In a few weeks we will be starting feature analysis for the MQ.next release. Its going to be the merging of the features of two JMS Products available from Sun (MQ and JMSGrid). The intention is to develop the product in a more open manner using OpenMessageQueue (
What are the features of the next release? Well, we aren't sure yet but at a minimum we will have to include:
- a file based HA story - which will provide message availability without the need for a highly available JDBC database
- Network Connections - the ability to connect to a remote cluster of brokers over a WAN connection
Note: this doesn't mean that support is going away for our current (JDBC) based HA implementation. Customer's using it now will not be left in the cold in the next release.
Tomorrow - I hope - I'll talk about HA and why we did it the way we did.