Vincenzo
Nota Bene: you can *force* resolution of a good version (<version>3.4.8</version>) to be used by all artifacts downstream from your parent pom.xml..the mechanism is called <dependencyManagement> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management Buona Fortuna Martini ______________________________________________ ________________________________ From: Vincenzo D'Amore <v.dam...@gmail.com> Sent: Saturday, December 3, 2016 12:14 PM To: users@kafka.apache.org Subject: Re: Suggestions I found what's wrong, well... finally! Given that consumer application shoul load received data into a Solr instance. Incidentally my version of Solr is SolrCloud, and Solrj client use zookeeper, a different version of zookeeper... Now I specified in my pom.xml the same version of zookeeper 3.4.8 I found in my kafka_2.11-0.10.1.0. overriding the original configuration, it seems work very well. So as far as I know now, this strange behaviour was due to a dependency problem. For sake of clarity, now I'm trying to restore original version of zookeeper just to be sure that the problem happens again. Thanks to everybody tried to help me. On Fri, Dec 2, 2016 at 8:50 PM, Apurva Mehta <apu...@confluent.io> wrote: > > > > then, the strange thing is that the consumer on > > the second topic which stay in poll forever, *without receive any > message*. > > > How long is 'forever'? Did you wait more than 5 minutes? > > On Fri, Dec 2, 2016 at 2:55 AM, Vincenzo D'Amore <v.dam...@gmail.com> > wrote: > > > Hi Kafka Gurus :) > > > > I'm creating process between few applications. > > > > First application create a producer and then write a message into a main > > topic (A), within the message there is the name of a second topic (B). > Then > > promptly create a second producer and write few message into the new > topic > > (B). > > > > I write here because I don't understand why, a second application which > is > > in poll on the main topic, when receive the first message (which contain > > the name of second topic), then, the strange thing is that the consumer > on > > the second topic which stay in poll forever, *without receive any > message*. > > > > What is wrong in this scenario, am I missing something? Please help. > > > > producer has this default properties: > > > > "bootstrap.servers":"localhost:9092", > > "acks":"all", > > "retries":0, > > "batch.size":16384, > > "linger.ms":1, > > "buffer.memory":33554432, > > > > "key.serializer":"org.apache.kafka.common.serialization.Stri > ngSerializer", > > > > "value.serializer":"org.apache.kafka.common.serialization. > > StringSerializer" > > > > consumer has this default properties: > > > > "bootstrap.servers":"localhost:9092", > > "enable.auto.commit":"true", > > "auto.commit.interval.ms":"1000", > > "session.timeout.ms":"30000", > > "buffer.memory":33554432, > > "key.deserializer": > > "org.apache.kafka.common.serialization.StringDeserializer", > > "value.deserializer": > > "org.apache.kafka.common.serialization.StringDeserializer" > > > > usually there are 2 active groups (group_A and group_B). > > > > Best regards, > > Vincenzo > > > > -- > > Vincenzo D'Amore > > email: v.dam...@gmail.com > > skype: free.dev > > mobile: +39 349 8513251 > > > -- Vincenzo D'Amore email: v.dam...@gmail.com skype: free.dev mobile: +39 349 8513251 <349%20851%203251>
