[ 
https://issues.apache.org/jira/browse/GEODE-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086626#comment-16086626
 ] 

ASF GitHub Bot commented on GEODE-2594:
---------------------------------------

GitHub user karensmolermiller opened a pull request:

    https://github.com/apache/geode/pull/635

    GEODE-2594 Remove tools.jar and --pid options from docs

    @kirklund @davebarnes97 @joeymcallister Please review.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/karensmolermiller/geode feature/GEODE-2594

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/geode/pull/635.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #635
    
----
commit 1ba8afeab1e8adbee5ed54fe75d0b751209c8651
Author: Karen Miller <[email protected]>
Date:   2017-07-14T00:00:53Z

    GEODE-2594 Remove tools.jar and --pid options from docs

----


> 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)

Reply via email to