[
https://issues.apache.org/jira/browse/KAFKA-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250342#comment-15250342
]
Greg Zoller commented on KAFKA-3568:
------------------------------------
Hi, Gwen... I am puzzled too. I didn't see any code that would account for
this, so I'm still not ruling out my methods as a cause.
I rebuilt both. Step #2 above is rebuilding the tgz core, which I then
unpacked into a Docker to run it. I modded the spotify/kafka Dockerfile as it
puts Kafka and Zookeeper conveniently in the same image. I then expose ports
9092 and 2181. Again, not ruling anything out here, but this does work for the
builds noted, including (now with my patch) the latest trunk build.
Step #4 builds and installs the clients to my local maven repo where my test
code picks it up. The test code is likewise always cleaned and rebuilt from
scratch to eliminate unwanted artifacts there.
My host is always 192.168.99.100:9092. I'm on a Mac so this IP address is my
VirtualBox IP (docker-machine ip default), and the two ports mentioned above
are configured to pass through VirtualBox to my Mac host. On the working
builds this functions without issue.
I was initially suspicious of a one-line change in build 73470b0 (Mar 22) that
commented out this line:
listeners=PLAINTEXT://:9092
It was really the only "active" change in this build, which is the first one
that stopped working for me. Aha! I though... this is it. So I un-commented
it out and to my surprise it was still broken. Out of raw frustration I cut 'n
pasted just the 4 other commented out lines from server.properties in that same
build. Further trial 'n error narrowed it down to the two mentioned above. I
got tired and didn't narrow it further to see if just one of these two made a
difference.
Still not trusting my methods, I thought i'd try the ultimate test... checking
out trunk raw and just pasting those two lines in and seeing what
happens....and that worked. Even ignoring the fact these are commented
out--the values are not meaningful.
I'm really hoping there's something else going on here. There's one other bug
that's kinda like this one. If I can find it I'll ask the poster what happens
if he tries this.
> KafkaProducer fails with timeout on message send()
> --------------------------------------------------
>
> Key: KAFKA-3568
> URL: https://issues.apache.org/jira/browse/KAFKA-3568
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 0.10.1.0
> Environment: MacOS Docker
> Reporter: Greg Zoller
> Labels: producer
>
> I had a KafkaProducer working fine in 0.9.0.1. I was having unrelated
> problems in that version so thought to try 0.10.1.0. I built it as I did
> 0.9.0.1:
> Fresh build against Scala 2.11.7. Built the tgz build plus local maven
> install. From the tgz I created a Docker image similar to spotify/kafka. I
> linked my producer code to the maven jars. This process worked in 0.9.
> Code is here:
> https://gist.github.com/gzoller/145faef1fefc8acea212e87e06fc86e8
> At the bottom you can see a clip from the output... there's a warning about
> metadata (not sure if its important or not) and then its trying to send()
> messages and timing out. I clipped the output, but it does fail the same way
> for each message sent in 0.10.1.0. Same code compiled against 0.9.0.1
> populates the topic's partitions w/o problem.
> Was there a breaking change between 0.9 and 0.10, or is this a bug?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
