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 B80F9200827 for ; Sun, 15 May 2016 10:13:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AB98A1609AD; Sun, 15 May 2016 08:13:14 +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 F1D7D160968 for ; Sun, 15 May 2016 10:13:13 +0200 (CEST) Received: (qmail 81030 invoked by uid 500); 15 May 2016 08:13:13 -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 81020 invoked by uid 99); 15 May 2016 08:13:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 May 2016 08:13:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E92062C1F58 for ; Sun, 15 May 2016 08:13:12 +0000 (UTC) Date: Sun, 15 May 2016 08:13:12 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CAMEL-9957) camel-kafka producer sends the message in an async way MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 15 May 2016 08:13:14 -0000 [ https://issues.apache.org/jira/browse/CAMEL-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283810#comment-15283810 ] Claus Ibsen commented on CAMEL-9957: ------------------------------------ The AsyncProcessor is extending Processor so if you implement AsyncProcessor you also get the synchronous processor. They are not separated. The producer is such an example as its both processor / async processor and therefore Camel routing engine will call favor calling the async processor method. There is no check if the processor was created from an endpoint that has a synchronous=true option. This option is not on the endpoint interface, but only an implementation detail on the default endpoint. Whether it would be an idea for Camel 3.0 to - separate Processor and AsyncProcessor - move synchronous as an option to endpoint interface is something we could consider. But for 2.x you could either - create 2 different producer implementations and in the endpoint in the createProducer method chose either the sync vs async implementation - use current code - refactor current code to be a bit better (which I am doing) and then the code is like what we do in other components that may have a forced synchronous mode. > camel-kafka producer sends the message in an async way > ------------------------------------------------------ > > Key: CAMEL-9957 > URL: https://issues.apache.org/jira/browse/CAMEL-9957 > Project: Camel > Issue Type: Improvement > Affects Versions: 2.17.1 > Reporter: Willem Jiang > Assignee: Willem Jiang > Fix For: 2.17.2, 2.18.0 > > > CAMEL-9790 made the sync sending, it could cause some trouble when ppl has lots of data to send. > We need to provide an async way to send the message to kafka. -- This message was sent by Atlassian JIRA (v6.3.4#6332)