activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Bertram <>
Subject Re: [DISCUSS] ActiveMQ {CodeName} Must-Have Features...
Date Wed, 15 Apr 2015 19:19:21 GMT
James, is this thread meant to discuss:

  A) the existing features from ActiveMQ 5.x that ActiveMQ {CodeName} would need to implement
really be considered the next generation of ActiveMQ
  B) the features that don't exist today in ActiveMQ that people would like to see in the
next generation (i.e. in ActiveMQ {CodeName})
  C) both 'A' and 'B'



----- Original Message -----
From: "Marc Schöchlin" <>
Sent: Wednesday, April 15, 2015 2:01:48 PM
Subject: Re: [DISCUSS] ActiveMQ {CodeName} Must-Have Features...


my whishlist:
(with descending importance level)

- stability and resilience!!!!!!!
- simplified configuration, (it should be difficult to create unstable
- easy and very stable out-of-the-box clustering without centralized
  (i.e. like leveldb but without running a dedicated zookeeper instance)
- a very good administration interface which operates on the
configuration files
- good operation system packages and integration
  (RPM, DEB and MSI packages )
- a good puppet module


Am 15.04.2015 um 17:56 schrieb James Carman:
> In order for ActiveMQ {CodeName} to take over as the next generation
> of ActiveMQ, it obviously must have some level of feature parity with
> the existing ActiveMQ 5.x (or 6.x if it's released before that
> transition) offering.  We should come up with some level of a roadmap
> together about which features are required.  Thus far, the only
> big-ticket items that have been addressed are:
> 1.  The OpenWire protocol is supported
> 2.  Auto-creation of destinations (mostly complete).
> This is obviously not all of what the existing ActiveMQ is all about.
> What other features are folks wanting to see in the next generation
> ActiveMQ?
> James

GPG encryption available: 0x670DCBEC/

View raw message