[
https://issues.apache.org/jira/browse/GEODE-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428984#comment-16428984
]
ASF subversion and git services commented on GEODE-4913:
--------------------------------------------------------
Commit 1be57f3d18e5a97dbcc784d6df7724f5f6ced39b in geode's branch
refs/heads/master from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1be57f3 ]
GEODE-4913: gfsh start server cmd is not recognizing local properties...
... and cache.xml, instead using default
Fixed DUnit test failures by reverting the test assertions as like earlier.
> 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)
