Summary: Verifying a local installation and a remote installation.
Overview To perform a simple system testing you should use the gsInstance.bat script on windows or gsInstance.sh script on linux.
Verifying Local Installation
- Run a single GigaSpaces space instance by moving to the <GigaSpaces Root>\bin directory and running the gsInstance.bat/sh command. You should see such an output:
D:\gigaspaces-xap-premium-7.1.2-ga\bin>gsInstance.bat
Starting a Space Instance
Setting space url to "/./mySpace?schema=default&properties=gs&groups="gigaspaces-7.1.2-XAPPremium-ga""
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Server VM (build 16.0-b13, mixed mode)
Log file: D:\gigaspaces-xap-premium-7.1.2-ga\bin\..\logs\2010-09-26~13.13-gigaspaces-service-HOST-6336.log
2010-09-26 13:13:59,473 INFO [com.gigaspaces.common.resourceloader] -
Loading properties file from: file:/D:/gigaspaces-xap-premium-7.1.2-ga/config/gs.properties
2010-09-26 13:14:00,126 INFO [com.gigaspaces.container] -
System Environment:
System:
OS Name: Windows Vista
OS Version: 6.0
Architecture: x86
Number Of Processors: 2
JVM Details:
Java Version: 1.6.0_18, Sun Microsystems Inc.
Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java VM: Java HotSpot(TM) Server VM 16.0-b13, Sun Microsystems Inc.
Java Home: D:\java\jdk1.6.0_18\jre
JVM Memory:
Max Heap Size (KB): 466048
Current Allocated Heap Size (KB): 47900
Network Interfaces Information:
Host Name: [HOST]
Network Interface Name: lo / Software Loopback Interface 1
IP Address: 0:0:0:0:0:0:0:1
IP Address: 127.0.0.1
Zones: N/A
Process Id: 6336
GigaSpaces Platform:
Edition: XAP Premium 7.1.2 GA
Build: 4600
Home: D:\gigaspaces-xap-premium-7.1.2-ga\bin\\..\
2010-09-26 13:14:01,290 INFO [com.gigaspaces.container] - Created RMIRegistry on: < HOST:10098 >
2010-09-26 13:14:01,321 INFO [com.gigaspaces.container] -
Webster HTTP server started successfully serving the following roots:
D:\gigaspaces-xap-premium-7.1.2-ga\bin\\..\/lib;D:\gigaspaces-xap-premium-7.1.2-ga\bin\\..\/lib/jini
Webster serving on: 192.168.1.131:9813
2010-09-26 13:14:02,469 INFO [com.sun.jini.reggie] -
started Reggie: 5b0dee88-984a-4280-a12b-683bb3cfb9ce, [gigaspaces-7.1.2-XAPPremium-ga], jini:2010-09-26 13:14:02,897 INFO [com.gigaspaces.core.common] -
Starting Space [mySpace_container:mySpace] with url
[/./mySpace?schema=default&properties=gs&groups=gigaspaces-7.1.2-XAPPremium-ga&state=started] ...
2010-09-26 13:14:04,072 INFO [com.gigaspaces.cache] -
Cache manager created with policy [ALL IN CACHE], persistency mode [memory]
2010-09-26 13:14:04,175 INFO [com.gigaspaces.cache] - Data source recovery:
Entries found in data source: 0.
Entries inserted to space: 0.
Entries under transaction: 0.
Total Time: 18 milliseconds.
2010-09-26 13:14:04,396 INFO [com.gigaspaces.core.common] -
Space [mySpace_container:mySpace] with url
[/./mySpace?schema=default&properties=gs&groups=gigaspaces-7.1.2-XAPPremium-ga&state=started] started successfully
- Make sure it loads without errors/exceptions. If you have error/exceptions check the following:
- JAVA_HOME environment variable - Make sure it points to a valid JDK folder.
- Network setup - Make sure the machine has a valid network interface installed with a valid IP.
- Multiple NICs - If your machine running multiple network interfaces, make sure you have the NIC_ADDR environment variable set to a valid IP of the machine. This should be done on every machine running GigaSpaces.
- User permissions - Make sure you run the gsInstnce.sh script with a linux user that has permissions to write into the <Gigaspaces root>/logs folder.
- CLASSPATH environment variable - Make sure the CLASSPATH environment variable is not specified. You might have some libraries specified as part of the CLASSPATH that cause GigaSpaces to fail.
- JSHOMEDIR - environment variable - Make sure the JSHOMEDIR environment variable is not specified or pointing to a different GigaSpaces release folder. It might be you have some other GigaSpaces release installed on the same machine with JSHOMEDIR variable pointing to this release folder.
- Ping the space by running the <GigaSpaces Root>\bin\gs.bat/sh utility:
 |
The following using multicast lookup discovery protocol. The first * of the URL means search for the lookup service across the network using multicast. |
The following result output should appear on the console:
D:\gigaspaces-xap-premium-7.1.2-ga\bin>gs space ping -url jini:total 1
ping from <mySpace> space
with:
Finder URL: jini:Lease Timeout: 10 seconds
LookupFinder timeout: 5000 milliseconds
Buffer Size: 100
Iterations: 5
Average Time = 135 milliseconds
 |
Subsequent space ping calls will have much faster response time. The fist space ping call introduce some meta data to the space. This happens only once. |
If the space ping call fails with the following:
total 0
Service is not found using the URL: jini:
You have the following options: – Make sure your network and machines running GigaSpaces are configured to have multicast enabled. See the How to Configure Multicast section for details on how to enable multicast. – Perform a space ping using unicast lookup discovery protocol:
The following result should appear on the console:
D:\gigaspaces-xap-premium-7.1.2-ga\bin>gs space ping -url jini:total 1
ping from <mySpace> space
with:
Finder URL: jini:Lease Timeout: 10 seconds
LookupFinder timeout: 5000 milliseconds
Buffer Size: 100
Iterations: 5
Average Time = 135 milliseconds
 |
When the ping client running on a remote machine (other than the machine running the space), localhost should be replaced with the machine hostname or IP running the space instance. |
Verifying Remote Installation Repeat the above steps #3, where the ping command is called from a machine different than the one running the space. You will have to install GigaSpaces both on the client and server machines. What's Next? Get Started with GigaSpaces Tutorials |