From issues-return-49678-archive-asf-public=cust-asf.ponee.io@camel.apache.org Mon Feb 26 09:54:04 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 F0AF618066D for ; Mon, 26 Feb 2018 09:54:03 +0100 (CET) Received: (qmail 86454 invoked by uid 500); 26 Feb 2018 08:54:03 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 86444 invoked by uid 99); 26 Feb 2018 08:54:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Feb 2018 08:54:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 8BABBC5F4D for ; Mon, 26 Feb 2018 08:54:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id M5qtT5JKyVWa for ; Mon, 26 Feb 2018 08:54:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id A37195FAC8 for ; Mon, 26 Feb 2018 08:54:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 09352E0956 for ; Mon, 26 Feb 2018 08:54:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5BBFC255CE for ; Mon, 26 Feb 2018 08:54:00 +0000 (UTC) Date: Mon, 26 Feb 2018 08:54:00 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CAMEL-11519) Add the ability for CAMEL-RABBITMQ to support transactional consumers and producers MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-11519?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D163= 76540#comment-16376540 ]=20 Claus Ibsen commented on CAMEL-11519: ------------------------------------- The patch seems to use a blocking thread when you wait to do a TX recovery = - is this a good solution? Then you block this on the client side. I wonder= if there is not a better solution on the server side, where you can do a r= ollback, and then let the broker "handle the redelivery and delay between r= edeliveries".=C2=A0 =C2=A0 > Add the ability for CAMEL-RABBITMQ to support transactional consumers and= producers > -------------------------------------------------------------------------= ---------- > > Key: CAMEL-11519 > URL: https://issues.apache.org/jira/browse/CAMEL-11519 > Project: Camel > Issue Type: Improvement > Components: camel-rabbitmq > Affects Versions: 2.19.1 > Reporter: Gary Motts > Priority: Minor > Labels: rabbitmq > Attachments: RabbitConsumer.patch, RabbitMQEndpoint.patch > > > Recommend enhancing the camel-rabbitmq component to optionally support tr= ansactional consumers and producers. As a temporary work around to make th= e consumer transactional, I added this.channel.txSelect(); to line 57 (ca= mel 2-19 branch) and this.channel.txCommit(); to line 133 and = this.channel.txRollback(); to line 165 of the RabbitMQConsumer. Recommen= d adding an endpoint option to disable or enable TX per channel -- This message was sent by Atlassian JIRA (v7.6.3#76005)