[jira] [Commented] (KAFKA-778) Fix unclear exceptions when the producer detects 0 partitions for a topic

[Zayeem (JIRA)]

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

Zayeem commented on KAFKA-778:
--

This is on 0.8 version.

In the test code, I am trying to check if the topic exists, if so , create 
producer and send a message. In the zookeeper shell, i can see that the topic 
exists under /brokers/topics/. However the listing 
/brokers/topics/ returns []

Here is the gradle dependency versions of my project

ext {
junitVersion = '4.10'
log4jVersion = '1.2.15'
mockitoVersion = '1.9.0'
springVersion = '3.1.3.RELEASE'
springIntegrationVersion = '2.2.0.RELEASE'
slfVersion = '1.6.4'
commonsPoolVersion = '1.6'
zooKeeperVersion = '3.3.4'
snappyVersion = '1.0.4.1'
scalaVersion = '2.9.2'
idPrefix = 'kafka'
}

> Fix unclear exceptions when the producer detects 0 partitions for a topic
> -
>
> Key: KAFKA-778
> URL: https://issues.apache.org/jira/browse/KAFKA-778
> Project: Kafka
>  Issue Type: Bug
>  Components: producer 
>Affects Versions: 0.8, 0.7.2
>Reporter: Neha Narkhede
>Assignee: Jun Rao
>
> ERROR [main][kafka.producer.async.DefaultEventHandler] Failed to collate
> messages by topic, partition due to
> kafka.common.NoBrokersForPartitionException: Partition key = null
> at
> kafka.producer.async.DefaultEventHandler.kafka$producer$async$DefaultEventHandler$$getPartitionListForTopic(DefaultEventHandler.scala:189)
>  at
> kafka.producer.async.DefaultEventHandler$$anonfun$partitionAndCollate$1.apply(DefaultEventHandler.scala:148)
> at
> kafka.producer.async.DefaultEventHandler$$anonfun$partitionAndCollate$1.apply(DefaultEventHandler.scala:147)
>  at
> scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:60)
> at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47)
>  at
> kafka.producer.async.DefaultEventHandler.partitionAndCollate(DefaultEventHandler.scala:147)
> at
> kafka.producer.async.DefaultEventHandler.dispatchSerializedData(DefaultEventHandler.scala:93)
>  at
> kafka.producer.async.DefaultEventHandler.handle(DefaultEventHandler.scala:72)
> at kafka.producer.Producer.send(Producer.scala:76)
>  at kafka.javaapi.producer.Producer.send(Producer.scala:41)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (KAFKA-751) Fix windows build script - kafka-run-class.bat

[Zayeem (JIRA)]

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

Zayeem commented on KAFKA-751:
--

With the patch, the server starts without any issues.

Previously, it runs into kafka.Kafka main class issues due to the 
non-availability of jars in the classpath.

> Fix windows build script - kafka-run-class.bat
> --
>
> Key: KAFKA-751
> URL: https://issues.apache.org/jira/browse/KAFKA-751
> Project: Kafka
>  Issue Type: Bug
>  Components: tools
>Affects Versions: 0.8
>Reporter: Mark deVilliers
>Priority: Minor
>  Labels: patch
> Fix For: 0.8
>
> Attachments: kafka-run-class.diff
>
>
> I've updated the kafka-run-class.bat to keep it in line (and working) with 
> the kafka-run-class.sh.
> I'll attach a diff file to the issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira