You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2015/05/13 11:25:00 UTC
[jira] [Commented] (ZOOKEEPER-2156) If JAVA_HOME is not set zk
startup and fetching status command execution result misleads user.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541648#comment-14541648 ]
Rakesh R commented on ZOOKEEPER-2156:
-------------------------------------
[~fournc] concerns has been addressed and committed the changes as part of ZOOKEEPER-2173. Now, I think we can take up this jira ahead.
[~rgs] since you had reviewed the patch earlier, would you be interested in reviewing the latest patch again:)
> If JAVA_HOME is not set zk startup and fetching status command execution result misleads user.
> ----------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2156
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2156
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: J.Andreina
> Assignee: J.Andreina
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2156.1.patch, ZOOKEEPER-2156.2.patch, ZOOKEEPER-2156.3.patch, ZOOKEEPER-2156.4.patch
>
>
> If JAVA_HOME is not set, zk startup and fetching status command execution result misleads user.
> 1. Eventhough zk startup has failed since JAVA_HOME is not set , on CLI it displays that zk STARTED.
> {noformat}
> #:~/Apr3rd/zookeeper-3.4.6/bin> ./zkServer.sh start
> JMX enabled by default
> Using config: /home/REX/Apr3rd/zookeeper-3.4.6/bin/../conf/zoo.cfg
> Starting zookeeper ... STARTED
> {noformat}
> 2. Fetching zk status when JAVA_HOME is not set displays that process not running .
> {noformat}
> #:~/Apr3rd/zookeeper-3.4.6/bin> ./zkServer.sh status
> JMX enabled by default
> Using config: /home/REX/Apr3rd/zookeeper-3.4.6/bin/../conf/zoo.cfg
> Error contacting service. It is probably not running.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)