HornetQ and ActiveMQ strategy?dpocock Feb 6, 2015 4:28 AM
I tried to reply in the topic about the 2.5.0.Beta1 but the forum is broken and won't let me. It tells me I may have reached some limit but I have only posted once in the last 24 hours, that was my question yesterday.
Thanks for the feedback about the beta, just to clarify, people should not be testing the 2.5.0.Beta1 tag at all then?
I understand you may not be keen to commit to a release date, but could you maybe provide some rough comments on some of the following:
If somebody starts a new project today, should they use the last stable HornetQ release or the last stable ActiveMQ release?
Will there be changes to ActiveMQ to make it more friendly for code that works against HornetQ? E.g. ActiveMQ has some different names for some of the MBeans (like message count), will it emulate the JMX names used by HornetQ or will I need to tweak all my JMXetric config files? I notice that STOMP clients also need to use a slightly different syntax for queue names with ActiveMQ, will it try to emulate the HornetQ naming conventions or will STOMP client code need to be modified?
I notice HORNETQ-1383 was fixed in 2.5.0.Beta1 and backported to 2.3.x but not 2.4.x. Is the 2.4.x branch going to be supported for any period of time?
For people who do continue using the HornetQ code base, will you still accept small bug fixes and things through Github pull requests and roll them up into maintenance releases? Or will it be completely abandoned?
I did some testing with the beta yesterday and I encountered an issue with authentication, JMS was always giving me "HT119031:Unable to validate user: guest" or "HT119031:Unable to validate user: null" and STOMP clients were not able to submit anything at all. Commenting out the <security-settings> stuff in the config and replacing it with <security-enabled>false</security-enabled> resolved the issues for both JMS and STOMP clients. Note that with the JMS clients, I would see an exception on both the client and server log but with the STOMP client there was no error logged.