Moving the export statement to kafka-server.start.sh fixed the issue. I was
able to start kafka with JMX monitoring and run kafka-topics.sh.
Thanks Lance.
On Mon, Sep 14, 2015 at 6:43 PM, Lance Laursen
wrote:
> This is not a bug. The java process spawned by kafka-topics.sh is trying to
> bind
This is not a bug. The java process spawned by kafka-topics.sh is trying to
bind to 9998 upon start. The java process spawned by kafka-server-start.sh
already owns that port. It's doing this because both of these scripts use
kafka-run-class.sh and that is where you defined your 'export JMX_PORT'.
After completely disabling JMX settings, i was able to create topics. Seems
like there is an issue with using JMX with the product. Should i create bug?
On Sun, Sep 13, 2015 at 9:07 PM, allen chan
wrote:
> Changing the port to 9998 did not help. Still the same error occurred
>
> On Sat, Sep 12,
Changing the port to 9998 did not help. Still the same error occurred
On Sat, Sep 12, 2015 at 12:27 AM, Foo Lim wrote:
> Try throwing
>
> JMX_PORT=9998
>
> In front of the command. Anything other than 9994
>
> Foo
>
> On Friday, September 11, 2015, allen chan
> wrote:
>
> > Hi all,
> >
> > Firs
Try throwing
JMX_PORT=9998
In front of the command. Anything other than 9994
Foo
On Friday, September 11, 2015, allen chan
wrote:
> Hi all,
>
> First time testing kafka with brand new cluster.
>
> Running into an issue that i do not understand.
>
> Server started up fine but I get error when
