You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Patrick Rhomberg (JIRA)" <ji...@apache.org> on 2017/09/25 20:38:00 UTC
[jira] [Updated] (GEODE-3590) Disconnect command fails to an NPE
when executed from the command line.
[ https://issues.apache.org/jira/browse/GEODE-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Rhomberg updated GEODE-3590:
------------------------------------
Labels: gfsh (was: )
> Disconnect command fails to an NPE when executed from the command line.
> -----------------------------------------------------------------------
>
> Key: GEODE-3590
> URL: https://issues.apache.org/jira/browse/GEODE-3590
> Project: Geode
> Issue Type: Bug
> Reporter: Patrick Rhomberg
> Assignee: Patrick Rhomberg
> Labels: gfsh
>
> Should a script desire to disconnect from one cluster and connect to another, it will fail without the continue-on-error option set.
> To reproduce:
> {noformat}
> $> gfsh -e "start locator" -e "disconnect"
> (1) Executing - start locator
> ....
> Locator in [...] is currently online.
> [Details banner]
> Successfully connected to: JMX Manager [host=10.118.33.172, port=1099]
> Cluster configuration service is up and running.
> (2) Executing - disconnect
> Disconnecting from: 10.118.33.172[1099]
> Error occurred while disconnecting: null
> {noformat}
> Cause of NPE is in the disconnect command, currently belonging to ShellCommands.disconnect:199 in the line
> {noformat}
> gfshInstance.setPromptPath(RegionPathConverter.DEFAULT_APP_CONTEXT_PATH);
> {noformat}
> which attempts to invoke a method on the member `reader`, which has not been initialized in headless mode.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)