[jira] [Comment Edited] (CAMEL-13630) KafkaProducer is force closed

["Yeldar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-13630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859819#comment-16859819 ] 

Yeldar edited comment on CAMEL-13630 at 6/10/19 8:31 AM:
---------------------------------------------------------

Hi Claus,

When I debugged the source I found out that after installation a bundle (camel+kafka) on karaf  server, a kafka-sender is initialized and method forceClose() is invoked after that.

Class: org.apache.kafka.clients.producer.internals.Sender
 Method: forceClose()

 

Thank you.


was (Author: turtle):
Hi Claus,

When I debugged the source I found out that after install a bundle (camel+kafka) on karaf a kafka sender will be initialized and method forceClose() is invoked after that.

Class: org.apache.kafka.clients.producer.internals.Sender
Method: forceClose()

 

Thank you.

> KafkaProducer is force closed
> -----------------------------
>
>                 Key: CAMEL-13630
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13630
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-kafka
>    Affects Versions: 3.0.0-M2
>         Environment:  - MacBook Pro 
>  - MacOS 10.13.6
>  - kafka kafka_2.11-2.2.0
>  - apache-karaf-4.2.5
> installed features in karaf
> feature:install webconsole
>  feature:repo-add camel 3.0.0-M3
>  feature:install camel
>  feature:install camel-blueprint
>  feature:install deployer
>  feature:install aries-blueprint
>  feature:repo-add hawtio 2.6.0
>  install mvn:org.apache.commons/commons-lang3/3.9
>  feature:install camel-sql
>  feature:install camel-jdbc
>  feature:install pax-jdbc-postgresql
>  install -s wrap:mvn:org.postgresql/postgresql/42.2.5
>  feature:install camel-jaxb
>  feature:install camel-servlet
>  feature:install war
> feature:install camel-kafka
>            Reporter: Yeldar
>            Priority: Minor
>         Attachments: issue.log
>
>
> Hi guys,
> We are working on transport project that based on karaf, camel, kafka and etc.
> Recently we bumped into a bug that doesn't allow keep on it. I debugged it and saw that the "sender" is always force-closed.
> I will try to explain to reproduce it by simple example:
> 1) We use a following blueprint:
>  
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="
> http://www.osgi.org/xmlns/blueprint/v1.0.0 https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd">
> <camelContext xmlns="http://camel.apache.org/schema/blueprint">
> <route id="DirectToKafka">
> <from uri="timer://foo?fixedRate=true&amp;period=5000"/>
> <setBody>
> <simple>Hello from Karaf Camel!</simple>
> </setBody>
> <log message="${in.body}"/>
> <setHeader headerName="kafka.PARTITION_KEY">
> <simple>0</simple>
> </setHeader>
> <setHeader headerName="kafka.KEY">
> <simple>1</simple>
> </setHeader>
> <to uri="kafka:myTopic?brokers=localhost:9092"/>
> <log message="${headers}"/>
> </route>
> </camelContext>
> </blueprint>
> {code}
>  2) The issue log is attached ("issue.log")
>  
> Could you please provide some information to fix the issue?
>  
> Thank you.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)