You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Barbara Pruijn (JIRA)" <ji...@apache.org> on 2018/02/13 20:53:00 UTC
[jira] [Resolved] (GEODE-4613) Gfsh's prints out error message
after shutdown --include-locators
[ https://issues.apache.org/jira/browse/GEODE-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barbara Pruijn resolved GEODE-4613.
-----------------------------------
Resolution: Fixed
> Gfsh's prints out error message after shutdown --include-locators
> -----------------------------------------------------------------
>
> Key: GEODE-4613
> URL: https://issues.apache.org/jira/browse/GEODE-4613
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Affects Versions: 1.4.0
> Reporter: Jinmei Liao
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Steps to reproduce:
> gfsh>start locator --name=locator
> gfsh>start server --name=server
> gfsh>shutdown --include-locators
> As a lot of data in memory will be lost, including possibly events in queues, do you really want to shutdown the entire distributed system? (Y/n): y
> Shutdown is triggered
> Failed to restart: java.io.IOException: Failed to get a RMI stub: javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in table]
> gfsh>
> No longer connected to 10.118.33.243[1099].
> Failed to call the method close():java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
> java.net.ConnectException: Connection refused (Connection refused)
> Failed to check connection: java.rmi.NoSuchObjectException: no such object in table
> stopping
> Error In gfsh.log:
> [severe 2018/02/06 13:53:33.931 PST JMX client heartbeat 2 tid=0x2d] (msgTID=45 msgSN=11) No longer connected to 10.118.33.243[1099].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)