Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E45CB200CAF for ; Thu, 22 Jun 2017 14:29:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E2F9E160BE7; Thu, 22 Jun 2017 12:29:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 33B81160BE5 for ; Thu, 22 Jun 2017 14:29:10 +0200 (CEST) Received: (qmail 72420 invoked by uid 500); 22 Jun 2017 12:29:09 -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 72406 invoked by uid 99); 22 Jun 2017 12:29:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2017 12:29:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 6E6E11A043C for ; Thu, 22 Jun 2017 12:29:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.794 X-Spam-Level: *** X-Spam-Status: No, score=3.794 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id G2olnjmFLzbe for ; Thu, 22 Jun 2017 12:29:06 +0000 (UTC) Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id DB27E5F2AC for ; Thu, 22 Jun 2017 12:29:05 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id p66so7858357oia.0 for ; Thu, 22 Jun 2017 05:29:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=bVY09Jgla3uca3gOxOUBwiGeljpbvwI4UhtA0r6q9G0=; b=BsP0BP43+GDShy9opE9cDxm2BCGqHy1TQQfBKjn61FryXO6SRFcVm5ggN0FPoBHKWi KYEmrAINnixFMoCH2pYomW3uborxZO9yKWX+6Yg3I25e0PddGSfcDcdQqNaamy7RnZGB xDw3X5wjzUon9GCmRWH0H/B0IrPoN1jtqzXstTBye72nixXRL1cdOuSlpqhSSeb3sENk TZp32VtuIxNewBUGWCREIUWhpe9eHeAHpMKbhxBsSZobSVTts15CPlXvQX9f5Wtr9xy6 e6QtZAYwSPNnpmBsegkrzdO1vX+Sn33ZerJT2h5e+sa4UKHLhrmYKAJI52D2PNI9Y234 g5Ig== X-Gm-Message-State: AKS2vOzvdTm99YDyqeSQfWiM2hAgHJP3hU6kpnmLfqgMwrRDT2i9jyga bqesH+m1j2Tp24wcYMDe73r21gqv8cJnK0E= X-Received: by 10.202.83.74 with SMTP id h71mr218249oib.135.1498134545039; Thu, 22 Jun 2017 05:29:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.76.10 with HTTP; Thu, 22 Jun 2017 05:29:04 -0700 (PDT) In-Reply-To: <1498129025702-4727734.post@n4.nabble.com> References: <1496663358135-4727014.post@n4.nabble.com> <1496907601462-4727185.post@n4.nabble.com> <1498129025702-4727734.post@n4.nabble.com> From: Justin Bertram Date: Thu, 22 Jun 2017 07:29:04 -0500 Message-ID: Subject: Re: Switch to Artemis from ActiveMQ v5.14.4? To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="001a113d12a4621aab05528ba111" archived-at: Thu, 22 Jun 2017 12:29:11 -0000 --001a113d12a4621aab05528ba111 Content-Type: text/plain; charset="UTF-8" > protocol interoperability is available but still It looks like code changes are required from the client side. What code changes are required for OpenWire clients to connect to Artemis? Please be as specific as possible. > Will clients using ActiveMQ client jar be able to connect to the broker running with Artemis ? Yes. > Currently clients uses ActiveMQConnectionFactory to initialize the connection factory and gets connections. Do they have to make changes if we switch broker to Artimis ? No, they shouldn't have to. Justin On Thu, Jun 22, 2017 at 5:57 AM, khandelwalanuj < anuj.cool.khandelwal@gmail.com> wrote: > Regarding interoperability: As you mentioned protocol interoperability is > available but still It looks like code changes are required from the client > side. > > To be more specific : Will clients using ActiveMQ client jar be able to > connect to the broker running with Artemis ? > > Eg: Currently clients uses ActiveMQConnectionFactory to initialize the > connection factory and gets connections. Do they have to make changes if we > switch broker to Artimis ? > > Thanks, > > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Switch-to-Artemis-from-ActiveMQ-v5-14-4-tp4727014p4727734.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --001a113d12a4621aab05528ba111--