Space Remote Access Issue

Having some problems trying to remotely connect to the space using unicast connections. Using 6.6.2 premium on vista x64, java 1.6.

Have followed the guide at [ http://www.gigaspaces.com/wiki/displa... ]

My space is running using

gs.bat -Dcom.gs.multicast.enabled=false -Dcom.gs.multicast.discoveryPort=7102 -Dcom.gigaspaces.system.registryPort=7103

setenv.bat set LOOKUPLOCATORS=192.168.1.96 set NIC_ADDR=192.168.1.96

services.config (note: what the doc tells you to do here doesn't work in 6.6.2) bindPort = System.getProperty("com.gs.transport_protocol.lrmi.bind-port", "10000-20000");

and I have my code deployed on the space.

gs-ui finds the space once I tell it to discover at 192.168.1.96:7102, I can deploy from here fine, so that all looks fine so far.

Problem comes when I try to connect a client to the space, my jini lookup looks like this

jini:////spaceFX?locators=192.168.1.96:7102

have also tried

IJSpace space = new UrlSpaceConfigurer("jini://192.168.1.96:7102//spaceFX?locators=192.168.1.96:7102*").space(); GigaSpace gigaSpace = new GigaSpaceConfigurer(space).gigaSpace();

The lookup is ok, but when I come to use the gigaSpace object (for say a read etc) I keep getting this exception -

WARNING [net.jini.discovery.LookupLocatorDiscovery]: Exception occured during unicast discovery to 192.168.1.96:4162 with constraints InvocationConstraints[reqs: {}, prefs: {}]. Please verify the unicast locators hostname and port are set properly. Caused by: java.net.ConnectException: Connection refused: connect 08-Jan-2009 15:27:04 INFO [com.gigaspaces.client]: Thread[main,5,main] No available members found - retrying 1

08-Jan-2009 15:27:05 WARNING [net.jini.discovery.LookupLocatorDiscovery]: Exception occured during unicast discovery to 192.168.1.96:4162 with constraints InvocationConstraints[reqs: {}, prefs: {}]. Please verify the unicast locators hostname and port are set properly. Caused by: java.net.ConnectException: Connection refused: connect

I must point out this is from the same machine as the space is running on, I'm assuming if this doesn't work then it won't from a remote machine. Quite why it's saying port 4162 failed when i'm telling it to use 7102 i'm not sure

  • what am I missing here?

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

asked 2009-01-08 09:37:35 -0600

aparry gravatar image

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

jaissefsfex gravatar image
edit retag flag offensive close merge delete