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

Anthony Baker closed GEODE-1884.
--------------------------------

> Users should be able to parse the output of gfsh start command
> --------------------------------------------------------------
>
>                 Key: GEODE-1884
>                 URL: https://issues.apache.org/jira/browse/GEODE-1884
>             Project: Geode
>          Issue Type: Improvement
>          Components: gfsh
>            Reporter: Swapnil Bawaskar
>            Priority: Major
>
> Geode servers can be started on a ephemeral port and the output does contain 
> the port number on which the server has started to listen, but the output is 
> not parseable for integration tests; example:
> {noformat}
> gfsh>start server --name=serv1 --server-port=0
> Starting a Geode Server in 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/serv1...
> ......
> Server in 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/serv1
>  on 192.168.0.21[57851] as serv1 is currently online.
> Process ID: 19039
> Uptime: 3 seconds
> GemFire Version: 1.0.0-incubating-SNAPSHOT
> Java Version: 1.8.0_45
> Log File: 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/serv1/serv1.log
> JVM Arguments: -Dgemfire.default.locators=192.168.0.21[10334] 
> -Dgemfire.use-cluster-configuration=true -Dgemfire.http-service-port=8080 
> -Dgemfire.start-dev-rest-api=false -XX:OnOutOfMemoryError=kill -KILL %p 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
> {noformat}
> The output of the above command needs to presented as a json so that it can 
> be parsed. We need an additional {{--output-format}} option to the start 
> server command:
> {noformat}
> gfsh start server --server-port=0 --output-format=json
> {noformat}
> which should result in the above output be returned as a json. The bind 
> address and the port should be available as separate elements in the json 
> output.



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

Reply via email to