You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Kenneth Howe (JIRA)" <ji...@apache.org> on 2017/07/20 21:21:00 UTC
[jira] [Assigned] (GEODE-3277) Gfsh commands throw
NumberFormatException when given wrong port number
[ https://issues.apache.org/jira/browse/GEODE-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Howe reassigned GEODE-3277:
-----------------------------------
Assignee: Kenneth Howe
Affects Version/s: 1.1.0
1.2.0
Component/s: gfsh
When given the {{--port}} option, gfsh attempts to connect to the specified port with a Status request through the {{LocatorLauncher}} (or {{ServerLauncher}}). If the request fails, then an error instance of {{LocatorState}} (or {{ServerState}}) is passed to the response builder. In the *State instance, the host, port, and location fields are null. When the response string is constructed, the exception is thrown when attempting to convert {{null}} to an integer string.
> Gfsh commands throw NumberFormatException when given wrong port number
> ----------------------------------------------------------------------
>
> Key: GEODE-3277
> URL: https://issues.apache.org/jira/browse/GEODE-3277
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Affects Versions: 1.1.0, 1.2.0
> Reporter: Kenneth Howe
> Assignee: Kenneth Howe
>
> The {{status locator}} and {{status server}} commands internally throw NumberFormatException, and print the message "null" on the console if the port specified with the {{--port=<number>}} option is not the correct port.
> The expected response should like:
> {code}
> Locator in <path> on 127.0.0.1[12346] is currently not responding.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)