[
https://issues.apache.org/jira/browse/KAFKA-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333020#comment-14333020
]
Ewen Cheslack-Postava commented on KAFKA-1680:
----------------------------------------------
Pretty sure this is still a bug. There's a default value for the JMX URL
setting, so it should be valid to run without passing any parameters. Of course
an alternative fix would be to remove that default value or make some other
setting required.
That said, the patch I posted addresses a much larger, far reaching bug across
all the command line tools -- a bunch were incorrectly checking for zero
command line arguments and exiting instead of allowing the options
parser/validation to determine when there were errors in the command line
arguments.
> JmxTool exits if no arguments are given
> ---------------------------------------
>
> Key: KAFKA-1680
> URL: https://issues.apache.org/jira/browse/KAFKA-1680
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.0
> Reporter: Ryan Berdeen
> Assignee: Ewen Cheslack-Postava
> Priority: Minor
> Labels: newbie
> Attachments: KAFKA-1680.patch
>
>
> JmxTool has no required arguments, but it exits if no arguments are provided.
> You can work around this by passing a non-option argument, which will be
> ignored, e.g.{{./bin/kafka-run-class.sh kafka.tools.JmxTool xxx}}.
> It looks like this was broken in KAFKA-1291 /
> 6b0ae4bba0d0f8e4c8da19de65a8f03f162bec39
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
