In general we are unable to post about forthcoming releases. However, I can confirm that we are continuing to work toward the features we discussed at JavaOne last year -- High Availability, JMX, JAAS, Etc. We're also looking at how we can leverage SJSMQ with some of Sun's recently acquired products.
Sadly, we're forbidden from discussing time frames unless you want to sign a confidential disclosure agreement.
We also are looking forward to moving Java System Message Queue (formerly iMQ ...), into Open Source. When that happens the notion of when, what feature is going to be available will be immediately transparent. We think that will be a good thing but ...
You could help us, by responding with your thoughts on open-sourcing Message Queue -- would that make the product more interesting to you? Would you be more, inclined to use SJSMQ if it were available as open source? The license likely would be as with many of our current open source offerings, CDDL, no support, no warranty, etc. Unless you purchase a license and support or another product which contains MQ (i.e. Sun Application Server, Java Enterprise System, Etc.).
Sorry, I can't be more specific about the features and timing, but do feel free to post your thoughts on open source.
Mate, I understand about making postings on upcoming features and releases. So thanks for taking the time to reply (and fairly comprehensively), that's really all I was looking for.
On the open source thing, I think it'd be great and would make me more likely to use the product. Where I work, we've recently had major issues with the product (in production); it's the possible the bug that was causing us grief would have been already addressed by an open-source project. Don't get me wrong, I know open-source is no silver bullet to all dev problems, I'm just saying it's possible.
There's a few puzzling things about Sun MQ such as the limited database support. This might also be addressed by an open-source model because you might get people with, say, mySQL or Postgres specialist knowledge more easily than within Sun -- or perhaps there'd be less corporate constraints on which DBs to support (I've no idea what kind of agreements or strictures Sun has in place about, say, use of DB2/UDB).
In a nutshell, I think it'd really help the product -- the sooner the better.
Our SQL support will be better tested with Open Source databases in forthcoming releases. Certainly, when we have moved to the Community Visible development arena, this will be a must.
If you would care to provide escalation, or bug-id(s) for the problem you are referring to, I could try to troubleshoot the response time from our end. I cannot guarantee that we'll do better, but we do consistently try to evaluate how we're doing and identify procedural things we can improve.
You can send this directly to me, if you like -- ed dot bratt at sun dot com.
-- Ed Bratt