You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Jeff Lord (JIRA)" <ji...@apache.org> on 2013/04/12 17:30:16 UTC

[jira] [Created] (ZOOKEEPER-1689) Remove JVMFLAGS completely from clients, if CLIENT_JVMFLAGS are also set

Jeff Lord created ZOOKEEPER-1689:
------------------------------------

             Summary: Remove JVMFLAGS completely from clients, if CLIENT_JVMFLAGS are also set
                 Key: ZOOKEEPER-1689
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1689
             Project: ZooKeeper
          Issue Type: Bug
          Components: scripts
    Affects Versions: 3.4.5
            Reporter: Jeff Lord
            Priority: Minor


In zkCli.sh, the CLIENT_JVMFLAGS are being passed along with regular JVMFLAGS, so the latter ends up overriding it anyhow if set. Can we please remove JVMFLAGS completely from clients, if CLIENT_JVMFLAGS are also set (i.e. use just one). 

One example of how this can be detrimental is if you attempt to start a zookeeper-client session on the same host that is already running zookeeper and use the default config directory. If the zookeeper server has jmx enabled than the client will also pick up that port and attempt to bind resulting in a failure

# /usr/bin/zookeeper-client 
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9010; nested exception is: 
java.net.BindException: Address already in use 


--
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