[
https://issues.apache.org/jira/browse/GEODE-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044754#comment-16044754
]
Jared Stewart commented on GEODE-3045:
--------------------------------------
The root issue as shown above is that the server attempting to start a JMX
manager gets a bind exception caused by a port conflict with the
already-started locator. It can be worked around by specifying
{noformat}--J=-Dgemfire.jmx-manager-port=X{noformat} where X is an available
port.
> Start server appears to hang
> ----------------------------
>
> Key: GEODE-3045
> URL: https://issues.apache.org/jira/browse/GEODE-3045
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh, management
> Reporter: Jared Stewart
>
> Steps to reproduce:
> {noformat}
> start locator --name=loc1
> {noformat}
> {noformat}
> start server --name=server1 --start-rest-api --J=-Dgemfire.jmx-manager=true
> --J=-Dgemfire.jmx-manager-start=true --J=-Dgemfire.http-service-port=8080
> {noformat}
> Then gfsh hangs with ".........." but the server has actually been started.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
