If you have Oracle JDK already installed, here is an example of how you could set it up:
*# Java 8* export JAVA_HOME=`/usr/libexec/java_home -v1.8` *# Java 7* export JAVA_HOME=`/usr/libexec/java_home -v1.7` # PATH export PATH=$JAVA_HOME/bin:$PATH On Mon, Jul 13, 2015 at 7:44 PM, William Markito <[email protected]> wrote: > It seems like it's using the Apple JVM, not Oracle. Please fix the > JAVA_HOME and the java binaries on path it will work. > > An easier way to do it is to download and install latest JDK 8 from Oracle > <http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html> > (Look for jdk-8u45-macosx-x64.dmg file) > > > On Mon, Jul 13, 2015 at 7:28 PM, Kirk Lund <[email protected]> wrote: > >> The start/status/stop commands attempt to use the Attach API if it's >> found. The latter is true if the JVM can classload >> com.sun.tools.attach.VirtualMachine. >> >> I suspect that your JVM found com.sun.tools.attach.VirtualMachine but >> cannot find sun.tools.attach.MacosxVirtualMachine which is surprising. >> Makes me wonder if your environment is somehow pointed at a tools.jar from >> a non-Mac OS such as linux. >> >> Hopefully someone more familiar with Mac OS X will weigh in on this. In >> the meantime, check your JRE and classpath. Make sure you're using a Mac OS >> X JRE and not including an outside tools.jar. >> >> If you cannot correct the problem any other way, you can try setting this >> system property: >> >> -Dgemfire.test.ProcessControllerFactory.DisableAttachApi=true >> >> That system property would need to be set in the gfsh JVM and also passed >> into each start/status/stop command that you launch from gfsh. >> >> 1) gfsh script >> >> Edit the "gfsh" script to add >> -Dgemfire.test.ProcessControllerFactory.DisableAttachApi=true to the last >> next to last line. >> >> 2) start commands >> >> Add the following argument to any start/status/stop command within gfsh: >> >> --J=-Dgemfire.test.ProcessControllerFactory.DisableAttachApi=true >> >> -Kirk >> >> >> On Mon, Jul 13, 2015 at 6:34 PM, darshan hs <[email protected]> wrote: >> >>> Locator issues >>> gfsh>start locator --name=locator >>> Starting a GemFire Locator in >>> /Users/hasudhakar/Desktop/node/Geode/incubator-geode/gemfire-assembly/build/install/apache-geode/locator... >>> An error occurred while attempting to start a Locator in >>> /Users/hasudhakar/Desktop/node/Geode/incubator-geode/gemfire-assembly/build/install/apache-geode/locator >>> on 192.168.0.5[10334]: Could not initialize class >>> sun.tools.attach.MacosxVirtualMachine >>> >>> Server Issues >>> gfsh>start server --name=server >>> Starting a GemFire Server in >>> /Users/hasudhakar/Desktop/node/Geode/incubator-geode/gemfire-assembly/build/install/apache-geode/server... >>> An error occurred while attempting to start a GemFire Cache Server: >>> Could not initialize class sun.tools.attach.MacosxVirtualMachine >>> >>> Hence the region issue >>> gfsh>create region --name=region --type=REPLICATE >>> "create region" is not available. Reason: Requires connection. >>> >>> Kindly help me resolve these >>> >> >> > > > -- > > William Markito Oliveira > Enterprise Architect > -- For questions about Apache Geode, please write to > *[email protected] > <[email protected]>* > > > -- William Markito Oliveira Enterprise Architect -- For questions about Apache Geode, please write to *[email protected] <[email protected]>*
