You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Swapnil Bawaskar (JIRA)" <ji...@apache.org> on 2018/04/09 22:37:15 UTC

[jira] [Closed] (GEODE-4913) gfsh start server cmd is not recognizing local properties and cache.xml, instead using default

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

Swapnil Bawaskar closed GEODE-4913.
-----------------------------------

> gfsh start server cmd is not recognizing local properties and cache.xml, instead using default
> ----------------------------------------------------------------------------------------------
>
>                 Key: GEODE-4913
>                 URL: https://issues.apache.org/jira/browse/GEODE-4913
>             Project: Geode
>          Issue Type: Bug
>          Components: configuration, gfsh
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Diane Hardman
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.5.0
>
>         Attachments: geode-script_10-31-2016.tgz
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> The attached tarfile contains scripts to start up 2 clusters and connect them with a WAN gateway.
>  The script for starting the servers for the first cluster (ln) fail because the default 40404 port is being used for each server. Instead, the start server command should be using the local cache.xml files found under config/gemfire-XX-hub.xml which contain:
> <cache-server port="0"/>
> This should force gfsh to choose the next available port, rather than the default 40404.
> It appears that the default cache.xml is being used. This problem does not exist with Geode 1.4.0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)