geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jared Stewart (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GEODE-3039) Start server gfsh arguments may conflict with --J=-D arguments
Date Tue, 06 Jun 2017 17:19:18 GMT
Jared Stewart created GEODE-3039:
------------------------------------

             Summary: Start server gfsh arguments may conflict with --J=-D arguments
                 Key: GEODE-3039
                 URL: https://issues.apache.org/jira/browse/GEODE-3039
             Project: Geode
          Issue Type: Bug
          Components: gfsh
            Reporter: Jared Stewart


{noformat}
    _________________________     __
   / _____/ ______/ ______/ /____/ /
  / /  __/ /___  /_____  / _____  / 
 / /__/ / ____/  _____/ / /    / /  
/______/_/      /______/_/    /_/    1.1.0

Monitor and Manage Apache Geode
gfsh>start server --name=server1 --J=-Dgemfire.start-dev-rest-api=true --J=-Dgemfire.http-service-bind-address=localhost
--J=-Dgemfire.jmx-manager=true --J=-Dgemfire.jmx-manager-start=true --J=-Dgemfire.http-service-port=8080
Starting a Geode Server in /Users/dbarnes/server1...
........................................
Server in /Users/dbarnes/server1 on 192.168.1.56[40404] as server1 is currently online.
Process ID: 1378
Uptime: 21 seconds
Geode Version: 1.1.0
Java Version: 1.8.0_101
Log File: /Users/dbarnes/server1/server1.log
JVM Arguments: -Dgemfire.use-cluster-configuration=true -Dgemfire.start-dev-rest-api=false
-Dgemfire.start-dev-rest-api=true -Dgemfire.http-service-bind-address=localhost -Dgemfire.jmx-manager=true
-Dgemfire.jmx-manager-start=true -Dgemfire.http-service-port=8080 -XX:OnOutOfMemoryError=kill
-KILL %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: /Users/dbarnes/geode11/lib/geode-core-1.1.0.jar:/Users/dbarnes/geode11/lib/geode-dependencies.jar
{noformat}

The user above has given `--J=-Dgemfire.start-dev-rest-api=true` as an argument to `start
server`.  This corresponds to the same option as the top-level parameter `--start-dev-rest-api`.
 Since this top-level parameter was unspecified, Spring Shell gave it a default value of false.
{noformat}
 @CliOption(key = StartServer.START_SERVER__REST_API, unspecifiedDefaultValue = "false",
          specifiedDefaultValue = "true",
          help = StartServer.START_SERVER__REST_API__HELP) final Boolean startRestApi,
{noformat}

This results in the command line for start server having both 
{noformat}
  -Dgemfire.start-dev-rest-api=false
    -Dgemfire.start-dev-rest-api=true
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message