activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (Commented) (JIRA)" <>
Subject [jira] [Commented] (APLO-166) when will be ready for accepting request from activemq 5.x jms clients
Date Mon, 27 Feb 2012 19:10:46 GMT


Hiram Chirino commented on APLO-166:

Once the OpenWire protocol if fully implemented and documented :) 

When will that be?  Since Apache is a volunteer organization, it's hard to say when it will
be completed.  I can just tell you what the current state its.  I would classify the current
state of the OpenWire Protocol as being alpha/beta quality.  It does not net support XA transactions
and not all use cases are fully unit tested.  Since the initial focus will be to to just make
it feature and backward compatible, we probably will not be focusing on optimizing the OpenWire
performance until thats done.

ActiveMQ development will NOT stop.  It has a large user based and we will continue to incrementally
improve that code base.  Apollo is jus providing a fresh new platform to do some things better.
> when will be ready for accepting request from activemq 5.x jms clients
> ----------------------------------------------------------------------
>                 Key: APLO-166
>                 URL:
>             Project: ActiveMQ Apollo
>          Issue Type: Question
>          Components: apollo-broker
>         Environment: linux, java 1.6
>            Reporter: Krishnadasan T S
> When will appollo will be ready for accepting jms based appi clients. I am  using activemq
5.5.1 in production environment. java,.net and cpp clients are connecting to activemq. Can
i migrate to appollo without any change in my client applications. What is the performance
improvement you expect for appolo over activemq. Will the current activemq development will
be stopped?. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message