[jira] [Updated] (GEODE-4774) When starting second locator without Security Manager, displaying incorrect status message

2018-03-09 Thread Barbara Pruijn (JIRA) 

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

Barbara Pruijn updated GEODE-4774:
--
Description: 
When I start a second locator without a Security Manager (inside a gfsh shell), 
I get the following output:
{code:java}
Security Manager is enabled - unable to auto-connect. Please use "connect 
--locator=10.118.19.11[13489]" to connect Gfsh to the locator.{code}
However, the output should state:
{code:java}
Cluster configuration service is up and running.{code}
How to reproduce:
{code:java}
gfsh>start locator --name=l1
Starting a Geode Locator in /Users/bpruijn/geode_tmp/l1...
...
Locator in /Users/bpruijn/geode_tmp/l1 on 10.118.19.45[10334] as l1 is 
currently online.
Process ID: 52871
Uptime: 3 seconds
Geode Version: 1.6.0-SNAPSHOT
Java Version: 1.8.0_151
Log File: /Users/bpruijn/geode_tmp/l1/l1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true 
-Dgemfire.load-cluster-configuration-from-dir=false 
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: 
/Users/bpruijn/workspace/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.6.0-SNAPSHOT.jar:/Users/bpruijn/workspace/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar

Successfully connected to: JMX Manager [host=10.118.19.45, port=1099]

Cluster configuration service is up and running.

gfsh>disconnect
Disconnecting from: 10.118.19.45[1099]
Disconnected from : 10.118.19.45[1099]

gfsh>start locator --name=l2 --port=13489
Starting a Geode Locator in /Users/bpruijn/geode_tmp/l2...

Locator in /Users/bpruijn/geode_tmp/l2 on 10.118.19.45[13489] as l2 is 
currently online.
Process ID: 52901
Uptime: 3 seconds
Geode Version: 1.6.0-SNAPSHOT
Java Version: 1.8.0_151
Log File: /Users/bpruijn/geode_tmp/l2/l2.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true 
-Dgemfire.load-cluster-configuration-from-dir=false 
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: 
/Users/bpruijn/workspace/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.6.0-SNAPSHOT.jar:/Users/bpruijn/workspace/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar

Security Manager is enabled - unable to auto-connect. Please use "connect 
--locator=10.118.19.45[13489]" to connect Gfsh to the locator.

gfsh>
{code}

Error in log:
{code}
[error 2018/03/09 14:17:14.977 PST l2  tid=0x23] Jmx 
manager could not be started because HTTP service failed to start
org.apache.geode.management.ManagementException: HTTP service failed to start
at 
org.apache.geode.management.internal.ManagementAgent.startHttpService(ManagementAgent.java:324)
at 
org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:149)
at 
org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:435)
at 
org.apache.geode.management.internal.JmxManagerLocator.findJmxManager(JmxManagerLocator.java:103)
at 
org.apache.geode.management.internal.JmxManagerLocator.processRequest(JmxManagerLocator.java:53)
at 
org.apache.geode.distributed.internal.InternalLocator$PrimaryHandler.processRequest(InternalLocator.java:1186)
at 
org.apache.geode.distributed.internal.tcpserver.TcpServer.processOneConnection(TcpServer.java:486)
at 
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:380)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at 
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at 
org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:334)
at 
org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:302)
at 
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at 
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:238)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:397)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at

[jira] [Updated] (GEODE-4774) When starting second locator without Security Manager, displaying incorrect status message

2018-03-06 Thread Barbara Pruijn (JIRA) 

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

Barbara Pruijn updated GEODE-4774:
--
Description: 
When I start a second locator without a Security Manager (inside a gfsh shell), 
I get the following output:
{code:java}
Security Manager is enabled - unable to auto-connect. Please use "connect 
--locator=10.118.19.11[13489]" to connect Gfsh to the locator.{code}
However, the output should state:
{code:java}
Cluster configuration service is up and running.{code}
How to reproduce:
{code:java}
gfsh> start locator --name=locator1
gfsh> start locator --name=locator2 --port=13489
{code}

  was:
When I start a second locator without a Security Manager, I get the following 
output:
{code:java}
Security Manager is enabled - unable to auto-connect. Please use "connect 
--locator=10.118.19.11[13489]" to connect Gfsh to the locator.{code}
However, the output should state:
{code:java}
Cluster configuration service is up and running.{code}

How to reproduce:
{code}
start locator --name=locator1
start locator --name=locator2 --port=13489
{code}


> When starting second locator without Security Manager, displaying incorrect 
> status message
> --
>
> Key: GEODE-4774
> URL: https://issues.apache.org/jira/browse/GEODE-4774
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Barbara Pruijn
>Priority: Major
>
> When I start a second locator without a Security Manager (inside a gfsh 
> shell), I get the following output:
> {code:java}
> Security Manager is enabled - unable to auto-connect. Please use "connect 
> --locator=10.118.19.11[13489]" to connect Gfsh to the locator.{code}
> However, the output should state:
> {code:java}
> Cluster configuration service is up and running.{code}
> How to reproduce:
> {code:java}
> gfsh> start locator --name=locator1
> gfsh> start locator --name=locator2 --port=13489
> {code}



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

[jira] [Updated] (GEODE-4774) When starting second locator without Security Manager, displaying incorrect status message

2018-03-05 Thread Barbara Pruijn (JIRA) 

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

Barbara Pruijn updated GEODE-4774:
--
Description: 
When I start a second locator without a Security Manager, I get the following 
output:
{code:java}
Security Manager is enabled - unable to auto-connect. Please use "connect 
--locator=10.118.19.11[13489]" to connect Gfsh to the locator.{code}
However, the output should state:
{code:java}
Cluster configuration service is up and running.{code}

How to reproduce:
{code}
start locator --name=locator1
start locator --name=locator2 --port=13489
{code}

  was:
When I start a second locator without a Security Manager, I get the following 
output:
{code:java}
Security Manager is enabled - unable to auto-connect. Please use "connect 
--locator=10.118.19.11[13489]" to connect Gfsh to the locator.{code}
However, the output should state:
{code:java}
Cluster configuration service is up and running.{code}


> When starting second locator without Security Manager, displaying incorrect 
> status message
> --
>
> Key: GEODE-4774
> URL: https://issues.apache.org/jira/browse/GEODE-4774
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Barbara Pruijn
>Priority: Major
>
> When I start a second locator without a Security Manager, I get the following 
> output:
> {code:java}
> Security Manager is enabled - unable to auto-connect. Please use "connect 
> --locator=10.118.19.11[13489]" to connect Gfsh to the locator.{code}
> However, the output should state:
> {code:java}
> Cluster configuration service is up and running.{code}
> How to reproduce:
> {code}
> start locator --name=locator1
> start locator --name=locator2 --port=13489
> {code}



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

[jira] [Updated] (GEODE-4774) When starting second locator without Security Manager, displaying incorrect status message

2018-03-05 Thread Barbara Pruijn (JIRA) 

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

Barbara Pruijn updated GEODE-4774:
--
Component/s: gfsh

> When starting second locator without Security Manager, displaying incorrect 
> status message
> --
>
> Key: GEODE-4774
> URL: https://issues.apache.org/jira/browse/GEODE-4774
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Barbara Pruijn
>Priority: Major
>
> When I start a second locator without a Security Manager, I get the following 
> output:
> {code:java}
> Security Manager is enabled - unable to auto-connect. Please use "connect 
> --locator=10.118.19.11[13489]" to connect Gfsh to the locator.{code}
> However, the output should state:
> {code:java}
> Cluster configuration service is up and running.{code}



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