Doh - wrong subject.

Is there any way to tell zkCli.sh to now register JMX or to not use port
8080 for it? It's conflicting with another process on our server.

-JZ

On 4/25/12 2:56 PM, "Jordan Zimmerman" <[EMAIL PROTECTED]> wrote:

>zkCli.sh seems to use port 8080. Is there any config/argument to change
>this? I couldn't find one. It's conflicting with another process on the
>machine.
>
>-JZ
>
>

On Wed, Apr 25, 2012 at 3:01 PM, Jordan Zimmerman
<[EMAIL PROTECTED]> wrote:
> Doh - wrong subject.
>
> Is there any way to tell zkCli.sh to now register JMX or to not use port
> 8080 for it? It's conflicting with another process on our server.

I don't think this is the case Jordan. I just ran zkCli from 3.4 and
no such port was used.

sudo netstat -anp

compare that to jps output?

Perhaps this is something in your environment? The client doesn't
explicitly start jmx, you might be able to pass an arg using
CLIENT_JVMFLAGS to zkCli.sh if you want to fiddle with some jvm
parameters.

Patrick

>
> On 4/25/12 2:56 PM, "Jordan Zimmerman" <[EMAIL PROTECTED]> wrote:
>
>>zkCli.sh seems to use port 8080. Is there any config/argument to change
>>this? I couldn't find one. It's conflicting with another process on the
>>machine.
>>
>>-JZ
>>
>>
>

On Wed, Apr 25, 2012 at 3:57 PM, Jordan Zimmerman
<[EMAIL PROTECTED]> wrote:
> FYI - here's the exception:
>
> Error: Exception thrown by the agent : java.rmi.server.ExportException:
> Port already in use: 8080; nested exception is:
>        java.net.BindException: Address already in use
>

This exception is generated by zkCli.sh? Can you edit the zkCli.sh
script with "set -x" near the top. Then send the exact java command
line that's being run. Might shed some light.

Perhaps CLIENT_JVMFLAGS or JVMFLAGS is set in your environment? (used
by zkCli.sh)

Patrick

On Wed, Apr 25, 2012 at 3:58 PM, Patrick Hunt <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 25, 2012 at 3:01 PM, Jordan Zimmerman
> <[EMAIL PROTECTED]> wrote:
>> Doh - wrong subject.
>>
>> Is there any way to tell zkCli.sh to now register JMX or to not use port
>> 8080 for it? It's conflicting with another process on our server.
>
> I don't think this is the case Jordan. I just ran zkCli from 3.4 and
> no such port was used.
>
> sudo netstat -anp
>
> compare that to jps output?
>
> Perhaps this is something in your environment? The client doesn't
> explicitly start jmx, you might be able to pass an arg using
> CLIENT_JVMFLAGS to zkCli.sh if you want to fiddle with some jvm
> parameters.
>
> Patrick
>
>>
>> On 4/25/12 2:56 PM, "Jordan Zimmerman" <[EMAIL PROTECTED]> wrote:
>>
>>>zkCli.sh seems to use port 8080. Is there any config/argument to change
>>>this? I couldn't find one. It's conflicting with another process on the
>>>machine.
>>>
>>>-JZ
>>>
>>>
>>