Summary: Verifying a local installation, a remote installation, and cluster configuration.

Overview

The GigaSpaces Server and utilities are configured to work on a default embedded space named mySpace (using the default schema), which is created during installation.

The space URL which is set as part of the gsInstance.bat also uses the default configuration overwrite properties file from:

<GigaSpaces Root>\config\gs.properties: set SPACE_URL="/./mySpace?schema=default&properties=gs"

Make sure your network and machines running GigaSpaces are configured to have multicast enabled. See the Multicast Configuration section for details on how to enable multicast.

For details on viewing the exact configuration in which the system is currently running, refer to the Container Maintenance section.

Verifying Local Installation

  1. Run the GigaSpaces Server by opening the <GigaSpaces Root>\bin directory and running the gsInstance.bat/sh command.
  2. It is recommended to verify the parameters in the <GigaSpaces Root>\bin\setenv.bat/sh file. Note that the VERBOSE variable is set to false in this file.
  3. Run gsInstance.bat/sh locally. Make sure it loads without errors/exceptions.
  4. Ping the space:
    • Run the space ping utility from the <GigaSpaces Root>\bin\gs.bat/sh prompt, using the following syntax (use your host ip/hostname instead of hostname):
      gs> space ping rmi://hostname:10098/mySpace_container/mySpace

      Here we verify the capability to ping to a local space, using RMI registry and specifying implicitly hostname:port.

      The following result should appear on the console:

      gs> space ping -url rmi://hostname:10098/mySpace_container/mySpace
      ping fromspace
      with:
      Finder URL: rmi://hostname:10098/mySpace_container/mySpace?timeout=5000
      Lease Timeout:  FOREVER
      LookupFinder timeout: 5000 milliseconds
      Buffer Size: 100
      Iterations: 5
      
      Average Time = 3 milliseconds

      If this stage fails, check if ping using Jini Multicast works:

    • Run the space ping utility from the <GigaSpaces Root>\bin\gs.bat/sh prompt, using the following syntax:
      gs> space ping jini://*/mySpace_container/mySpace

      Here we verify the capability to ping to a local space, using Multicast Jini Lookup Service.

      The following result should appear on the console:

      gs> space ping -url jini://*/mySpace_container/mySpace
      total 1
      ping fromspace
      with:
      Finder URL: jini://*/mySpace_container/mySpace?timeout=5000
      Lease Timeout:  FOREVER
      LookupFinder timeout: 5000 milliseconds
      Buffer Size: 100
      Iterations: 5
      
      Average Time = 0 milliseconds

      If this stage fails, check if ping is using Jini Unicast works:

    • Run the space ping utility from the <GigaSpaces Root>\bin\gs.bat/sh prompt, using the following syntax (use your host ip/hostname instead of hostname):
      gs> space ping jini://hostname/mySpace_container/mySpace

      Here we verify the capability to ping to a local space, using Unicast Jini Lookup Service.

      The following result should appear on the console:

      gs> space ping -url jini://hostname/mySpace_container/mySpace
      total 1
      ping fromspace
      with:
      Finder URL: jini://hostname/mySpace_container/mySpace?timeout=5000
      Lease Timeout:  FOREVER
      LookupFinder timeout: 5000 milliseconds
      Buffer Size: 100
      Iterations: 5
      
      Average Time = 0 milliseconds

      If the ping utility displays the following error:

      gs> space ping -url jini://hostname/mySpace_container/mySpace
      total 0
      Service is not found using the URL: jini://hostname/mySpace_container/mySpacej?timeout=5000

      make sure you have not disabled the JNDI or the Jini Lookup Service as part of your installation process.

      You can do this by checking the jndi and the jini sections in your <GigaSpaces Root>\config\schemas\default-container-schema.xml file.

  5. Check if multicast is enabled in the host, using the defined address. In most cases it is 224.0.0.1:
    ping 224.0.0.1

    The ping referred to in this step is a regular ping, not the space ping CLI utility.

  6. Test multicast using the in-house multicast CLI utility – see admin multicastTest*** for details on how to run the test.

Verifying Remote Installation

Repeat steps 1 - 4, but from a remote host.

Verifying Cluster Configuration

  1. To verify one of the cluster configurations, run the startAll.bat/sh command from the <GigaSpaces Root>\examples\Advanced\Data_Grid\replicated\bin directory.
  2. Run the space list CLI utility using the following syntax (use your host ip/hostname instead of hostname):
    gs> space list -url jini://hostname/rep_cache_container1/rep_cache -cluster
    

    Here we verify the capability to launch and list typical cluster configuration of two nodes.

  3. The following result should appear on the console:
    <gs> space list -url jini://hostname/rep_cache_container1/rep_cache -cluster
    Space name  objects count  templates count  secured clustered primary  persistent state  schema   jini group 
    container name     hostname
    ----------------------------------------------------------------------------------------------------------------------
    rep_cache   24             0                   No      Yes      Yes      No      started default  gigaspaces-6.0XAP 
    rep_cache_container1 alexb-lt
    Cluster schema: sync_replicated
    
    URL: /./rep_cache?schema=default&cluster_schema=sync_replicated&total_members=2&id=1&groups=gigaspaces-6.0XAP
    
    Class Name: com.j_spaces.core.cluster.PingEntry Objects count: 4        Templates count: 0
    Class Name: com.gigaspaces.admin.cli.Ping$Message       Objects count: 20       Templates count: 0
    
    ----------------------------------------------------------------------------------------------------------------------
    rep_cache   24             0                   No      Yes       Yes     No      started default  gigaspaces-6.0XAP  
    rep_cache_container2 alexb-lt
    Cluster schema: sync_replicated
    
    URL: /./rep_cache?schema=default&cluster_schema=sync_replicated&total_members=2&id=2&groups=gigaspaces-6.0XAP
    
    Class Name: com.j_spaces.core.cluster.PingEntry Objects count: 4        Templates count: 0
    Class Name: com.gigaspaces.admin.cli.Ping$Message       Objects count: 20       Templates count: 0
    
    ----------------------------------------------------------------------------------------------------------------------
    
  4. You should be able to see the two replication nodes in the list: rep_cache_container1 and rep_cache_container2.

What's Next?

Get Started with GigaSpaces 6.6 Tutorials

***Link required

GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence