[
https://issues.apache.org/jira/browse/GEODE-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087789#comment-16087789
]
ASF GitHub Bot commented on GEODE-2594:
---------------------------------------
Github user karensmolermiller commented on a diff in the pull request:
https://github.com/apache/geode/pull/635#discussion_r127524976
--- Diff: geode-docs/configuring/running/running_the_locator.html.md.erb ---
@@ -35,7 +35,7 @@ You can run the locator standalone or embedded within
another Geode process. Run
Locator configuration and log files have the following properties:
-- When you start a standalone locator using `gfsh`, `gfsh` will
automatically load the required JAR files
(`$GEMFIRE/lib/locator-dependencies.jar`) into the CLASSPATH of the JVM
process. If you start a standalone locator using the `LocatorLauncher` API, you
must specify `$GEMFIRE/lib/locator-dependencies.jar` inside the command used to
launch the locator process. For more information on CLASSPATH settings in
Geode, see [CLASSPATH Settings for Geode
Processes](../../getting_started/setup_classpath.html). You can modify the
CLASSPATH by specifying the `--classpath` parameter.
+- When you start a standalone locator using `gfsh`, `gfsh` will
automatically load the required JAR file
(`$GEMFIRE/lib/locator-dependencies.jar`) into the CLASSPATH of the JVM
process. If you start a standalone locator using the `LocatorLauncher` API, you
must specify `$GEMFIRE/lib/locator-dependencies.jar` inside the command used to
launch the locator process. For more information on CLASSPATH settings in
Geode, see [CLASSPATH Settings for Geode
Processes](../../getting_started/setup_classpath.html). You can modify the
CLASSPATH by specifying the `--classpath` parameter.
--- End diff --
That task is being tracked with Geode-3208.
> Remove optional usage of Attach API
> -----------------------------------
>
> Key: GEODE-2594
> URL: https://issues.apache.org/jira/browse/GEODE-2594
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
> Reporter: Kirk Lund
> Assignee: Karen Smoler Miller
> Labels: StartCommand, StatusCommand, StopCommand, gfsh
> Fix For: 1.2.0
>
>
> This is a request to remove our optional usage of Attach API.
> Users keep running into issues caused by GFSH using the Attach API. If the
> user kills a GemFire process that was started by GFSH, the Attach API leaves
> a java_pid file in /tmp which prevents the Attach API from working with any
> future JVMs that reuse that pid. Most users also want to use a JRE without
> the tools.jar.
> The only functionality that will be removed is status and stop command
> support for --pid option.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
