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 36371200CAF for ; Thu, 22 Jun 2017 13:14:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3304B160BE7; Thu, 22 Jun 2017 11:14: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 7635F160BE5 for ; Thu, 22 Jun 2017 13:14:09 +0200 (CEST) Received: (qmail 29697 invoked by uid 500); 22 Jun 2017 11:14:08 -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 29684 invoked by uid 99); 22 Jun 2017 11:14:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2017 11:14:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 629F8192716 for ; Thu, 22 Jun 2017 11:14:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.488 X-Spam-Level: *** X-Spam-Status: No, score=3.488 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id wQUqMpztTmRJ for ; Thu, 22 Jun 2017 11:14:06 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 5DDB160CCB for ; Thu, 22 Jun 2017 11:14:06 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id AEAC54C4BAF1F for ; Thu, 22 Jun 2017 04:14:00 -0700 (MST) Date: Thu, 22 Jun 2017 03:57:05 -0700 (PDT) From: khandelwalanuj To: users@activemq.apache.org Message-ID: <1498129025702-4727734.post@n4.nabble.com> In-Reply-To: References: <1496663358135-4727014.post@n4.nabble.com> <1496907601462-4727185.post@n4.nabble.com> Subject: Re: Switch to Artemis from ActiveMQ v5.14.4? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Thu, 22 Jun 2017 11:14:10 -0000 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.