From users-return-49829-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Mon Apr 9 14:33:38 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 14065180645 for ; Mon, 9 Apr 2018 14:33:37 +0200 (CEST) Received: (qmail 79453 invoked by uid 500); 9 Apr 2018 12:33:36 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 79442 invoked by uid 99); 9 Apr 2018 12:33:36 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Apr 2018 12:33:36 +0000 Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id C86AE1D1D for ; Mon, 9 Apr 2018 12:33:35 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id 71-v6so7387596oie.12 for ; Mon, 09 Apr 2018 05:33:35 -0700 (PDT) X-Gm-Message-State: ALQs6tD2fyqSimhsz7WSfNuEp6XSZnztW0DzxEYop4H8yM1Ct5VkUgW9 dFGeeV/VwVWyMNzY/+wkgwMHB/swdOQU7Fe3zgCyJQ== X-Google-Smtp-Source: AIpwx49MjmuOpdQGos8+8vI6n4x+dRkUBAUdeGQe1bG/rHW8+35HFVpq2bzYRVaxrFwkRGTcHNC3fiXCzVfPsCgw6eQ= X-Received: by 2002:aca:cfc8:: with SMTP id f191-v6mr20682525oig.134.1523277214812; Mon, 09 Apr 2018 05:33:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.168.12 with HTTP; Mon, 9 Apr 2018 05:33:34 -0700 (PDT) In-Reply-To: <1523250879727-0.post@n4.nabble.com> References: <1522907503362-0.post@n4.nabble.com> <1523250879727-0.post@n4.nabble.com> From: Justin Bertram Date: Mon, 9 Apr 2018 07:33:34 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Replicated Message Store for ActiveMQ To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="00000000000048a29e0569699dfd" --00000000000048a29e0569699dfd Content-Type: text/plain; charset="UTF-8" ActiveMQ Artemis fully implements the JMS specification so any client using JMS (e.g. Apache Camel) should work without issues. For what it's worth, Artemis ships with an example [1] using Apache Camel for bridging messages between a 5.x broker instance and an Artemis instance. The ActiveMQ 5.x has a lot of features, some of which are commonly used and some of which aren't. The goal isn't 100% feature parity, but feature parity where it makes sense. I believe most of the big use-cases are covered. If you could clarify your particular use case(s) then I could provide a more specific answer. I don't understand what you mean by "durability of Artemis." Can you elaborate on this question? Justin [1] https://github.com/apache/activemq-artemis/tree/master/examples/features/sub-modules/inter-broker-bridge/artemis-jms-bridge#5x-to-artemis-camel-jms-bridge On Mon, Apr 9, 2018 at 12:14 AM, SubashKunjupillai wrote: > Hi Tim, > > Thanks for your suggestions. > > Saying that, moving to ActiveMQ Artemis would be the ideal option. I'm also > not sure whether all the features being used by us (camel routes are used > to > produce and consume JMS messages) with ActiveMQ 5.14.4 will be available in > ActiveMQ Artemis 2.5.0. > > From community perspective can some one comment on the feature > compatibility > and durability of Artemis? > > Regards, > Subash Kunjupillai > > > > ----- > Subash Kunjupillai > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html > --00000000000048a29e0569699dfd--