Lookup Service Configuration
Defining group names and unicast Locators for Jini Services; searching for available lookup services in the network.
It is essential to set the
locators system properties in the Java process which starts the Lookup Service or Mahalo services. This is required in order to “tell” the Jini service which groups and locators it should join, and which to serve. If these properties are not set, the Lookup Service/Mahalo uses the Jini fallback values and that impact the SLA these services serve with.
Do not have more than two Jini Lookup Services across one site - having the
space-instance running a Jini Lookup Service embedded by default can cause problems. As a result of not have more than two Jini Lookup Services across one site, spaces do not have to deal with registering themselves into too many Jini Lookup Services, and the Space Browser’s freezing behavior is reduced.
Jini groups vs. locators - Jini groups are irrelevant when using unicast lookup discovery - they are relevant only when using multicast lookup discovery. If you have multiple spaces with the same name and you are using unicast lookup discovery, you might end up getting the wrong proxy.
In such a case, make sure you have a different lookup group for each space, where each space is configured to use a specific lookup. A good practice is to have different space/service names.
When using multicast please review the following section How to Determine Whether Multicast is Available and How to Configure Multicast.
Setting up the Lookup Service For Multicast Discovery (Using Lookup Group)
Each of the Jini Services (such as the Reggie lookup service or the Mahalo Transaction Manager) registers and advertises using a group name which is defined by the following system property (set in the
set XAP_LOOKUP_GROUPS="gigaspaces-%USERNAME%" set LOOKUP_GROUPS_PROP=-Dcom.gs.jini_lus.groups=%XAP_LOOKUP_GROUPS%
%USERNAME% will be replaced after installation with the version number e.g.
The command that loads a space needs to have this system property set. Another way of doing it instead of setting the
com.gs.jini_lus.groups system property, is to set the Space URL groups attribute, e.g.:
If you are looking for a way to use a unicast discovery, please refer to the How to Configure Unicast Discovery section for more details.
To support co-existence of different XAP versions, the defaults below may change between releases.
Adjusting the lookup services multicast settings can be done using the following system properties:
|com.gs.multicast.enabled||Global property allowing you to completely enable or disable multicast in the system.||true|
|com.gs.multicast.announcement||the multicast address that controls the lookup service announcement. The lookup service uses this address to periodically announce its existence.||184.108.40.206|
|com.gs.multicast.request||the multicast address that controls the request of clients (when started) to available lookup services.||220.127.116.11|
|com.gs.multicast.discoveryPort||the port used during discovery for multicast requests. Defaults to 4174. Note that in case the property com.sun.jini.reggie.initialUnicastDiscoveryPort system property is not defined it is also used as the default post for unicast requests.||4174|
|com.gs.multicast.ttl||The multicast packet time to live.||3|
The two multicast addresses allow you to completely separate two different GigaSpaces installations, so lookup services won’t communicate with each other (even on the wire level, which is different than the groups, which communicate on the content level).
Troubleshooting the Discovery/Group Configuration
Using the list LUS CLI option, run from
<XAP Root>\bin\gs.bat/sh, you can search for available Jini Lookup Services in the network.
<XAP Root>\bin\gs.bat/sh list lus
The following result examples appear on the console:
----------------------------------------------------------------------- -- Discovered Lookup Service at host [ 192.168.10.233 ]. -- Lookup Service registered to the following jini groups: Group [ gigaspaces-gershon ] -- Lookup Service has  services, lookup took  millis,  seconds: Service Class: com.j_spaces.core.JSpaceContainerProxy | 018aae08-5d2a-4b61-9739-36c915f4e2d9 Service Class: com.j_spaces.core.client.JSpaceProxy | 6f05db92-187f-4e26-b52d-ec32d3d4723c Service Class: com.sun.jini.reggie.ConstrainableRegistrarProxy | 2ff6aab3-8e1a-4a2b-a1b2- 4391825c2bbc ----------------------------------------------------------------------- -- Discovered Lookup Service at host [ 192.168.10.233 ]. -- Lookup Service registered to the following jini groups: Group [ gigaspaces-gershon ] -- Lookup Service has  services, lookup took  millis,  seconds: Service Class: com.j_spaces.core.JSpaceContainerProxy | 018aae08-5d2a-4b61-9739-36c915f4e2d9 Service Class: com.j_spaces.core.client.JSpaceProxy | 6f05db92-187f-4e26-b52d-ec32d3d4723c Service Class: com.sun.jini.reggie.ConstrainableRegistrarProxy | d3e7e224-9b46-4782-a902- e4e64c11ca95
Multi Network Card Configuration
For details on multi-network card configuration, refer to: How to Configure an Environment With Multiple Network-Cards (Multi-NIC).