[
https://issues.apache.org/jira/browse/CAMEL-13630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859962#comment-16859962
]
Yeldar commented on CAMEL-13630:
--------------------------------
Hi Claus,
I would like to describe about simple steps for reproduce (2 min):
1) Before, I test my current environment, I was working on the project that use
Camel 2.23.2 and all's good. I can produce and consume messages to and from
Kafka. Karaf 4.2.5, Kafka kafka_2.11-2.2.0 and Zookeeper were started.
2) I stoped just current karaf, unpack new karaf instance, started and install
following features:
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:install camel-kafka
3) I copied file "karaf-camel-kafka.xml" into directory "deploy" of new karaf
instance and got the issue.
I'm attaching the file "karaf-camel-kafka.xml" and karaf log.
[^karaf-camel-kafka.xml]
[^karaf.log]
There is no issues with network, because it work for Camel 2.23.2 and doesn't
work for Camel 3.0.0-M3 on my laptop.
You can reproduce it on several minutes and if you need some additional
information don't hesitate ask me.
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, karaf-camel-kafka.xml, karaf.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&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)
