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 04901200CD2 for ; Thu, 27 Jul 2017 20:44:48 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0302A16B506; Thu, 27 Jul 2017 18:44:48 +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 482EA16B4FE for ; Thu, 27 Jul 2017 20:44:47 +0200 (CEST) Received: (qmail 62690 invoked by uid 500); 27 Jul 2017 18:44:41 -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 62679 invoked by uid 99); 27 Jul 2017 18:44:41 -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, 27 Jul 2017 18:44:41 +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 BA1071805B5 for ; Thu, 27 Jul 2017 18:44:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.793 X-Spam-Level: *** X-Spam-Status: No, score=3.793 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, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id oiygvFy_yx3A for ; Thu, 27 Jul 2017 18:44:38 +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 005845F2F1 for ; Thu, 27 Jul 2017 18:44:37 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id g131so114970248oic.3 for ; Thu, 27 Jul 2017 11:44:37 -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=9Lvj1+4nixnng8ORDbBfe7Ri8xaeXwoqYW6f57I4yi4=; b=VqcWTpcAdZU9RX0fRvfnfY7tWDqKnVzEB5hnGCzNFbYeiDSjVCBpNaVid5XWKMKqL5 vbA3RVPwZ9I6/7QJ9mSLVJQHFzDb3YHmDvEBJhsLC2nJy+OpL0Ib17UK+M1OkumRToTw QlIwxRDgmUZv0YMPGs7K694t0opCQmj+92MKXkepGwU59lupTA719+a9hFtCoEVxHz9w 5nxEjYRrin1h2NYO76gHxERUEs5uE/eWVSCrLTgKuoi6cjziIh8mtbn0xQ1S0F7qUQY8 1I92Dq0h13mUltajt9g5kKxMsG6cCEDJt99G9O2g88p6XB9eCDc2/Obe0lBdX3tSn0o6 63sA== X-Gm-Message-State: AIVw1104Sl2pXRZjwuJFN8jvPTLoe9qsVcFEUVOl8lM096S5Ktgjz6wm jdXpsRFZD1FBClAxsJ4tss4PueT2B0JM X-Received: by 10.202.84.200 with SMTP id i191mr5032455oib.267.1501181071240; Thu, 27 Jul 2017 11:44:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.171.131 with HTTP; Thu, 27 Jul 2017 11:44:30 -0700 (PDT) In-Reply-To: References: <1501082187962-4728934.post@n4.nabble.com> <1501176837821-4728978.post@n4.nabble.com> From: Justin Bertram Date: Thu, 27 Jul 2017 13:44:30 -0500 Message-ID: Subject: Re: Artemis: AMQP bridges To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="001a113dd1747ec677055550f495" archived-at: Thu, 27 Jul 2017 18:44:48 -0000 --001a113dd1747ec677055550f495 Content-Type: text/plain; charset="UTF-8" Clebert, are you changing the core bridge to support Artemis' internal AMQP message representation or are you implementing a bridge that uses the AMQP protocol? Justin On Thu, Jul 27, 2017 at 1:19 PM, Clebert Suconic wrote: > On Thu, Jul 27, 2017 at 2:07 PM Justin Bertram > wrote: > > > Thanks for the explanation. That seems like it would be a good use-case > > for Camel bridging between two JMS providers. > > > > Regardless I will have to fix the core bridge to load balance amqp as well. > > > > > > > Justin > > > > On Thu, Jul 27, 2017 at 12:54 PM, Clebert Suconic < > > clebert.suconic@gmail.com > > > wrote: > > > > > Check back in a week. I'm working on it. > > > > > > On Thu, Jul 27, 2017 at 1:34 PM adagys wrote: > > > > > > > Thanks, I'll have a look at Dispatch. > > > > > > > > The use-case is a distributed ledger platform, where we have a > > > peer-to-peer > > > > network of nodes operated by different parties. Each node runs an > > Artemis > > > > broker, and maintains queues for messages to other nodes, which get > > > > forwarded using core bridges. We'd like to support a scenario where > > some > > > of > > > > the nodes run a non-Artemis AMQP broker, and it's still possible to > > > > interoperate (the non-Artemis broker might also require some > additional > > > > bridging support). > > > > > > > > For more context: > > > > https://docs.corda.net/key-concepts-ecosystem.html#network-structure > > > > network-structure> > > > > > > > > > > > > > > > > -- > > > > View this message in context: > > > > http://activemq.2283324.n4.nabble.com/Artemis-AMQP- > > > bridges-tp4728934p4728978.html > > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > > > > -- > > > Clebert Suconic > > > > > > -- > Clebert Suconic > --001a113dd1747ec677055550f495--