[
https://issues.apache.org/jira/browse/CAMEL-13630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008073#comment-17008073
]
Federico Valeri commented on CAMEL-13630:
-----------------------------------------
Hi, just tried with Camel 3.0.0 on Karaf 4.2.7 and it seems to work fine.
I'm attaching the project that includes a small README with instructions.
{code}
karaf@root()> camel:route-list
Context Route Status Total # Failed #
Inflight # Uptime
------- ----- ------ ------- --------
---------- ------
camel-1 DirectToKafka Started 18 0
0 1 minute
{code}
Retrieving some messages with console-consumer:
{code}
$ bin/kafka-console-consumer.sh --bootstrap-server localhost:9092
--from-beginning --topic myTopic --max-messages 10
Hello from Karaf Camel!
Hello from Karaf Camel!
Hello from Karaf Camel!
Hello from Karaf Camel!
Hello from Karaf Camel!
Hello from Karaf Camel!
Hello from Karaf Camel!
Hello from Karaf Camel!
Hello from Karaf Camel!
Hello from Karaf Camel!
Processed a total of 10 messages
{code}
> KafkaProducer is force closed on karaf
> --------------------------------------
>
> 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
(v8.3.4#803005)
