[ https://issues.apache.org/jira/browse/GEODE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Baker updated GEODE-780: -------------------------------- Fix Version/s: (was: 1.0.0-incubating) 1.0.0-incubating.M2 > GFSH should not require Attach API to start Locators or Servers > --------------------------------------------------------------- > > Key: GEODE-780 > URL: https://issues.apache.org/jira/browse/GEODE-780 > Project: Geode > Issue Type: Bug > Components: management > Reporter: Kirk Lund > Assignee: Kirk Lund > Fix For: 1.0.0-incubating.M2 > > > {noformat} > gfsh>start locator --name=locator1 > Starting a GemFire Locator in > C:\dev\geode\gemfire-assembly\build\install\apache > -geode\bin\locator1... > An error occurred while attempting to start a Locator in > C:\dev\geode\gemfire-as > sembly\build\install\apache-geode\bin\locator1 on > klund-e6420.vmware.com[10334]: > The Attach API classes could not be found on the classpath. Please include > JDK > tools.jar on the classpath or add the JDK tools.jar to the jre/lib/ext > director > y. > {noformat} > The current code uses an alternative implementation for status and stop if > Attach API is missing. The start command should not attempt to use > statusWithPid since it knows the working directory of the process being > launched. > The error should only occur when attempting to use --pid with a status or > stop command when the Attach API is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)