The goal of this page is to identify the outstanding issues that must be addressed by Artemis in order to achieve some level of feature parity with ActiveMQ 5.x. The overall objective for working toward feature parity between ActiveMQ 5.x and Artemis is for Artemis to eventually become ActiveMQ 6.x. This page exists so that we can work together as a group to achieve this goal.
Using this page
Feature items can be listed, with links to JIRA tickets for longer conversation and hashing out specific feature details
Table of Contents
Work in Progress
This page is a work in progress and will be updated frequently.
Support full-duplex broker-to-broker cluster connections [
Destination Policy: Garbage collection and advisory support for that activity [
Destination Policies (there is a slew of functionality in ActiveMQ 5.x dest policies that should be detailed out)
Support for multiple shared persistence stores similar to multi-kahadb (allow for storage across multiple disk volumes.. ie. queue://ORDER.> on /mnt/order queue://BILLING.> on /mnt/billing, etc) [
This section should help to answer the end user question, 'How do I migrate from ActiveMQ 5.x to Artemis?'. This should include the identification of any tools that can help make this easier, as well as documenting information and procedures specific to migrating.