JMX Port Conflict when starting both Broker and kafka Connect

[harish lohar <hk...@gmail.com>]

Hi ,

I am trying to use kafkaConnect for mongdb-source-connector

I am using connect-distributed.sh.

When i start kafka with KAFKA_JMX_OPTS, kafka broker starts fine but as
soon as kafka connect is started it gives
javaagent:./jmx_prometheus_javaagent-0.6.jar=7071:./kafka-0-8-2.yml"

address already in use error as below:

2018-11-30 10:08:18.142:WARN:ipjsoejuc.AbstractLifeCycle:FAILED
SelectChannelConnector@0.0.0.0:7071: java.net.BindException: Address
already in use
java.net.BindException: Address already in use

Please let me know if there is any configuration change exist to avoid this
conflict.

Thanks
Harish

Re: JMX Port Conflict when starting both Broker and kafka Connect

[Sruthi Kumar Annamneedu <sr...@gmail.com>]

Hi Harish,

     Using netstat command, see which process is using the port.
See if following steps help:
- If processA is intended to use portX which is having issues, stop processA
- If the processB is using the port, then stop ProcessB
- Restart processB and try using the port
- Restart the processA

See if it helps. Example for netstat command is: netstat -anp | grep
<port#>.

Best,
Sruthi Kumar

On Fri, Nov 30, 2018 at 10:10 AM harish lohar <hk...@gmail.com> wrote:

> Hi ,
>
> I am trying to use kafkaConnect for mongdb-source-connector
>
> I am using connect-distributed.sh.
>
> When i start kafka with KAFKA_JMX_OPTS, kafka broker starts fine but as
> soon as kafka connect is started it gives
> javaagent:./jmx_prometheus_javaagent-0.6.jar=7071:./kafka-0-8-2.yml"
>
> address already in use error as below:
>
> 2018-11-30 10:08:18.142:WARN:ipjsoejuc.AbstractLifeCycle:FAILED
> SelectChannelConnector@0.0.0.0:7071: java.net.BindException: Address
> already in use
> java.net.BindException: Address already in use
>
> Please let me know if there is any configuration change exist to avoid this
> conflict.
>
> Thanks
> Harish
>