Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question

Another question about "Replication Over WAN"


If the space in LN1 fail and I don't want the space reborn in San Francisco, I use 2 Jini lookup locators ,2GSM ,2GSC (using unicast discovery) to prevent this.

However, I cannot replicate the objects between LN1 and SF1 after I use 2 Jini lookup locators.

I have try to eliminate network problem by deploy 2 Jini lookup locators ,2GSM ,2GSC and 4 spaces(LN1 ,LN2 ,SF1 and SF2) in one machine. But the problem is still there.

So, what is wrong in this situation? Or, what is the recommended solution to prevent space reborn in wrong place?

Sorry for the poor English

Edited by: Tsui Chi wing on Feb 26, 2009 2:43 AM

{quote}This thread was imported from the previous forum. For your reference, the original is [available here|http://forum.openspaces.org/thread.jspa?threadID=2907]{quote}

asked 2009-02-26 02:39:20 -0600

cwtsui gravatar image

updated 2013-08-08 09:52:00 -0600

jaissefsfex gravatar image
edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

How do you deploy this using GSC and GSM?
How your pu.xml looks like?

answered 2009-02-26 13:47:02 -0600

shay hassidim gravatar image
edit flag offensive delete link more

I am sorry. I forget to change * to host:port in static cluster configure file

answered 2009-02-26 04:09:57 -0600

cwtsui gravatar image
edit flag offensive delete link more


#first set up LOOKUPLOCATORS export LOOKUPLOCATORS="IP:4162" #then disable multicast / enable unicast export EXT_JAVA_OPTIONS="-Xmx512m -Dcom.gs.multicast.enabled=false" start Jini lookup service ./gs.sh start com.gigaspaces.start.services="LH" OR ./startJiniLUS.bat\sh start GSM ( must do that because ./gsm.bat\sh start both Jini lookup service and GSM ) ./gs.sh start com.gigaspaces.start.services="GSM" start GSC ./gs.sh start com.gigaspaces.start.services="GSC" OR ./gsc.bat\sh

In my case, 2 groups does not really separated oversea. They are just located in two rooms. I just don't want the space in one room reborn in another room.

Two Jini lookup groups seems not suitable. Using two Jini lookup groups, if the machine in one room die,

  • connecting application still running (although Exception message is print out, object can be read, write and notify)
  • new connection will be fail if the application is using the old Jini Url

As I want it to be transparent to users, it approach is not suitable. Is there any method to keep all the things in same Jini lookup groups and restrict the location of space reborn??

cwtsui gravatar image cwtsui  ( 2009-02-26 21:14:44 -0600 )edit

When you use the LOOKUPLOCATORS this means you use unicast discovery. In this case the whole jini groups nation is irrelevant and is not supported.

If you want a space to be provisioned into a specific machine you should use platform capabilities - i.e. run the GSC with an override file as an argument - See GSC override file example below:

<overrides> <component name="org.jini.rio.qos"> <parameter name="addPlatformCapabilities"> new org.jini.rio.qos.capability.software.SoftwareSupport( new Object[]{"Name", "LocationX"}) } ]]> </parameter> </component> </overrides>

And have the space pu.xml to have the following: <os-sla:sla> <os-sla:requirements> <os-sla:system name="SoftwareSupport"> <os-sla:attributes> <entry key="Name" value="LocationX"/> </os-sla:attributes> </os-sla:system> </os-sla:requirements> </os-sla:sla>

This how the deployed space will be provisioned only to a GSC which have the PlatformCapability - Name=LocationX

See more here: http://www.gigaspaces.com/wiki/displa...


shay hassidim gravatar image shay hassidim  ( 2009-02-27 15:29:58 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2009-02-26 02:39:20 -0600

Seen: 127 times

Last updated: Feb 26 '09