Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Thu, 15 Dec 2016 08:04:58 +0000 (UTC)
From: "Tom Pijl (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.13028313.1481787400000.527267.1481789098324@Atlassian.JIRA>
In-Reply-To: <JIRA.13028313.1481787400000@Atlassian.JIRA>
References: <JIRA.13028313.1481787400000@Atlassian.JIRA> <JIRA.13028313.1481787400506@arcas>
Subject: [jira] [Updated] (ZOOKEEPER-2645) If embedded QuorumPeerMain is
 started with Properties no backupOldConfig should be done
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 15 Dec 2016 08:05:00 -0000


     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Pijl updated ZOOKEEPER-2645:
--------------------------------
    Priority: Major  (was: Blocker)

> If embedded QuorumPeerMain is started with Properties no backupOldConfig should be done
> ---------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2645
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2645
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.5.2
>            Reporter: Tom Pijl
>
> When starting an embedded _QuorumPeerMain_ by executing the _runFromConfig()_ and providing _QuorumPeerConfig_ properties:
> {code}standaloneEnabled=false
> initLimit=5
> syncLimit=2
> clientPort=4101
> server.1=nlbantpijl01.infor.com:2101:3101:participant;4101
> dataDir=/Storage/zookeeper/server001{code}
> an NullPointerException is thrown in the _QuorumPeerConfig_ class in the method _backupOldConfig()_ because the property configFileStr is null.
> A check must be made at the start of the method _backupOldConfig()_ if the property _configFileStr_ is null. If so just exit the method. In the embedded mode there is no config file, so no need to create a backup.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)