[jira] [Resolved] (GEODE-1681) gfsh start server should support more gemfire properties

["Barbara Pruijn (JIRA)" <ji...@apache.org>]

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

Barbara Pruijn resolved GEODE-1681.
-----------------------------------
    Resolution: Fixed

> gfsh start server should support more gemfire properties
> --------------------------------------------------------
>
>                 Key: GEODE-1681
>                 URL: https://issues.apache.org/jira/browse/GEODE-1681
>             Project: Geode
>          Issue Type: Improvement
>          Components: gfsh
>            Reporter: Darrel Schneider
>            Priority: Major
>
> The gfsh start server command needs more options for the gemfire properties.
> It has support for a bunch of them but for others customers need to add "--J=-Dgemfire.". If you make a typo in the system property name you will not get any indication of it.
> A user recently was setting the following: "--J=-Dgemfire.start-dev-rest-api=true --J=-Dgemfire.http-service-bind-address=10.205.84.13 --J=-Dgemfire.http-service-bind-port=8081  --J=-Dgemfire.jmx-manager=true --J=-Dgemfire.jmx-manager-start=true"
> They should have been able to do this instead: "--start-dev-rest-api=true --http-service-bind-address=10.205.84.13 --http-service-bind-port=8081  --jmx-manager=true --jmx-manager-start=true" and would have been told that "--http-service-bind-port" was an unknown option (it should have been "-http-service-port").
> It seems like it would be best for gfsh start server to support all the gemfire properties that are in the ConfigurationProperties class.



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