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 9DBC6200B9F for ; Tue, 11 Oct 2016 12:07:58 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9C3BC160AE6; Tue, 11 Oct 2016 10:07:58 +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 D2498160AD2 for ; Tue, 11 Oct 2016 12:07:57 +0200 (CEST) Received: (qmail 755 invoked by uid 500); 11 Oct 2016 10:07:52 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Delivered-To: moderator for users@camel.apache.org Received: (qmail 84069 invoked by uid 99); 11 Oct 2016 10:00:22 -0000 X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.486 X-Spam-Level: *** X-Spam-Status: No, score=3.486 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, URI_HEX=1.313] autolearn=disabled Date: Tue, 11 Oct 2016 03:00:16 -0700 (MST) From: habdank To: users@camel.apache.org Message-ID: <1476180016282-5788592.post@n5.nabble.com> Subject: Kafka component reports wrong metadata MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 11 Oct 2016 10:07:58 -0000 Dears, I am using Camel 2.17. I am starting my Kafka route and Kafka component is started indirectly. Parametrisation is very simple: In my log files Kafka components states the following: Is not clear why it is so, but it is definitely wrong. I would expect proper values and not id: -1 and empty partition list. After printing this info I see log entry like: And I had proven that Kafka works well by using Kafka's build in producer consumer. So connecting to Kafka cluster shall result in receiving proper metadata. What can be the reason for this? Is it a bug in logging? Best regards, Seweryn. -- View this message in context: http://camel.465427.n5.nabble.com/Kafka-component-reports-wrong-metadata-tp5788592.html Sent from the Camel - Users mailing list archive at Nabble.com.