Space Url Properties

The following are optional property string values that can be used as part of a Space Url.

Property String Description Optional values
* Used with Jini protocol to indicate any host or container name  
/./ Start the space in local embedded mode  
fifo Indicates that all take/write operations be conducted in FIFO mode. Default is false. Example: jini://localhost:10098/*/spaceName?fifo=true true| false
groups The Jini Lookup Service group to find container or space using multicast. Example: jini://*/*/spaceName?groups=grid
This is the lookup group which the space and Jini Transaction Manager register with, and which clients use by default to connect to the space.
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 for each space, where each space is configured to use a specific lookup. A good practice is to have different space names.
Group name
locators Instructs the started space or a client to locate the Jini Lookup Service on specific host name and port.  
jini: Using JINI Lookup service to search for the space  
updateMode Push or pull update mode. Example: jini://localhost:10098/*/spaceName?useLocalCache&updateMode=1 UPDATE_MODE_PULL = 1
UPDATE_MODE_PUSH = 2
rmi: Using RMI Lookup service to search for the space  
timeout The max timeout in [ms] to find a Container or Space using multicast
jini:// protocol. Default: 60000[ms] Example: jini://*/*/spaceName?timeout=10000
 
useLocalCache Turn Master-Local Space mode.By default Master-Local mode is turned off. To enable master local have the useLocalCache as part of the URL
versioned When false, optimistic lock is disabled. In a local cache and views the default is true, otherwise the default value is false. Example: jini://localhost:10098/*/spaceName?versioned=false  
cluster_schema The cluster schema XSL file name to be used to setup a cluster config on the fly in memory. If the ?cluster_schema option is passed e.g. ?cluster_schema=sync_replication, the system will use the sync_replication-cluster-schema.xsl together with a cluster Dom which will be built using user's inputs on regards # of members, # of backup members etc.  
schema Using the schema flag, the requested space schema name will be loaded/parsed while creating an embedded space. If the space already has configuration file then the requested schema will not be applied and the that file exist, it will overwrite the default configuration defined by the schema. Note that when using the option ?create with java:// protocol, the system will create a container, space and use the default space configuration schema file (default-space-schema.xml)  
total_members The total_members attribute in the space URL stands for the total number of cache members within the cache cluster.
The number is used to create the list of members participating in the cluster on the fly based on the cache name convention. This pattern is used to avoid the need for creating a cluster topology file.
The number of actual running cache instances can vary dynamically between 1<=total_members.
The format of the total_members =number of primary instances, number of backup instances per primary. In this example the value is 4,2 which means that this cluster contains up to 4 primary instances each containing 2 backup instances. The backup_id is used to define whether the instance is a backup instance or not.
If this attribute is not defined the instance will be considered a primary instance. The container name will be translated in this case to [cache name]_container[id][backup_id].
In this case it will be expanded to mySpace_container1_1
 
backup_id Used in case of Partitioned Cache (when adding backup to each partition). The backup_id is used to define whether the instance is a backup instance or not. If this attribute is not defined the instance will be considered a primary cache instance.
The container name will be translated in this case to [cache name]container[id][backup_id].
In this case it will be expanded to mySpace_container1_1.
 
NOWriteLease If true - Lease object would not return from the write/writeMultiple operations. Default: false  
id The id attribute is used to distinguish between cache instances in this cluster.  
properties if properties property is used as part of the URL space, space and container schema will be loaded and the properties listed as part of the properties file ([prop-file-name].properties) which contains the values to override the schema space/container/cluster configuration values that are defined in the schema files.  
mirror When setting this Url property it will allow the space to connect to the Mirror service to push its data and operations for asynchronous persistency.
Example:
/./spaceName?cluster_schema=sync_replicated&mirror
Default: no mirror connection
 

Example for space Url using Space Url options:

jini://*/*/mySpace?useLocalCache&versioned=false
/./mySpace?cluster_schema=partitioned&total_members=4&id=1
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence