Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F2E8811B98 for ; Wed, 27 Aug 2014 05:30:00 +0000 (UTC) Received: (qmail 49031 invoked by uid 500); 27 Aug 2014 05:30:00 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 48998 invoked by uid 500); 27 Aug 2014 05:30:00 -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 48986 invoked by uid 99); 27 Aug 2014 05:30:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Aug 2014 05:30:00 +0000 Date: Wed, 27 Aug 2014 05:30:00 +0000 (UTC) From: "Willem Jiang (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CAMEL-7500) Concurrent modification of exchange during retry after netty TCP failure leads to futher processing of failed messages MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-7500: -------------------------------- Fix Version/s: Future > Concurrent modification of exchange during retry after netty TCP failure leads to futher processing of failed messages > ---------------------------------------------------------------------------------------------------------------------- > > Key: CAMEL-7500 > URL: https://issues.apache.org/jira/browse/CAMEL-7500 > Project: Camel > Issue Type: Bug > Components: camel-netty > Affects Versions: 2.13.1 > Reporter: Bob Browning > Assignee: Willem Jiang > Fix For: Future > > Attachments: NettyRedeliveryTest.java > > > When a exception occurs on a netty TCP channel such as ChanelClosedException then there are two invocations of the producer callback. > If there is a redelivery handler configured this causes either two threads to be added to the scheduled thread-pool which then compete or in the more common case the first invocation adds the redelivery thread but in doing so clears the exception from the exchange such that when the subsequent callback invocation occurs it see's the event as a success and continues routing of the exchange. > Note this also seems to be a cause of negative inflight messages on the route. > The first callback invocation occurs in the ChannelFutureListener which is the usual case. > The second callback invocation which comes from the ClientChannelHandler registered in the DefaultClientPipelineFactory used by the NettyProducer. -- This message was sent by Atlassian JIRA (v6.2#6252)