Problem with discovery on XAP 7.0.2

I've installed 7.0.2 on a linux server on the 172.16.100.x network, started up a GSC and a GSM, which registered properly. But on my dev machine, on the 192.168.x.x network assigned by DHCP, I can't see the linux server. The UI causes an exception on the GSC:

2010-02-02 08:30:07,769 LUS INFO [com.sun.jini.reggie] - failed to resolve host LAPTOP_JOTTINGE; connection will still be attempted; Caused by: java.net.UnknownHostException: LAPTOP_JOTTINGE 2010-02-02 08:30:07,770 LUS INFO [com.sun.jini.reggie] - failed to respond to [] on port 28,679; Caused by: java.net.UnknownHostException: LAPTOP_JOTTINGE

(My working machine is, obviously, LAPTOP_JOTTINGE.)

If I configure the hosts file such that it can find my laptop by name, I no longer get the exception - but the UI still doesn't show the GSC or the GSM.

With 6.6.4 all of this worked fine, although that GSM is on Windows. What am I missing? h4. Attachments

[2010-02-02~08.27-gigaspaces-lh_gsm-ssclbeta-21764.log|/upfiles/13759706505292606.txt]

[2010-02-02~08.27-gigaspaces-gsc-ssclbeta-21915.log|/upfiles/13759706509580706.txt]

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

asked 2010-02-02 07:40:33 -0600

jottinger
1 ●2

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

jaissefsfex
1 ●1

Before running the GS-UI set its NIC_ADDR to have the machine IP.
This will allow the lookup and GSM to send notifications back to the GS-UI.

See more here:
http://www.gigaspaces.com/wiki/display/SBP/MovingintoProductionChecklist

Shay

answered 2010-02-02 10:35:17 -0600

shay hassidim

17818 ●8 ●12 ●16

edit flag offensive delete link

Comments

Done, but while it now doesn't give me an error in the console, the UI still doesn't show the GSM or GSC.

jottinger ( 2010-02-02 14:09:20 -0600 )edit

Actually, there's more here. We use openspaces, so we're using the jini lookup from the spring configuration.

The clients are going to be NATted, so they won't know the IP that they will look like to the GSM; their internal (actual) IP might be 172.16.100.1, while the GSM would see the packet as if it were from 172.16.2.101.

We can set the apparent NIC address from the client, because we expose a service that tells the local machine what it looks like from a NATted perspective, but how would we do that for openspaces?

jottinger ( 2010-02-02 14:28:35 -0600 )edit

Have you tried to set the java.rmi.server.hostname property? This should be set to have IP that is accessible by the relevant process. That's what the NIC_ADDR variable is doing. Shay

shay hassidim ( 2010-02-02 18:54:38 -0600 )edit

No, I haven't - but wouldn't that have the same problem? The device would have to know the IP that the server could use to access it.

jottinger ( 2010-02-02 20:53:11 -0600 )edit

Please contact support to resolve this.
Shay

shay hassidim ( 2010-02-03 06:52:55 -0600 )edit

add a comment

Your Answer

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

Problem with discovery on XAP 7.0.2

[2010-02-02~08.27-gigaspaces-lh_gsm-ssclbeta-21764.log|/upfiles/13759706505292606.txt]

[2010-02-02~08.27-gigaspaces-gsc-ssclbeta-21915.log|/upfiles/13759706509580706.txt]

1 Answer

Comments

Your Answer

Question Tools

Stats

Related questions

Problem with discovery on XAP 7.0.2 edit

[2010-02-02~08.27-gigaspaces-lh_gsm-ssclbeta-21764.log|/upfiles/13759706505292606.txt]

[2010-02-02~08.27-gigaspaces-gsc-ssclbeta-21915.log|/upfiles/13759706509580706.txt]

1 Answer

Comments

Your Answer

Question Tools

Stats

Related questions

Problem with discovery on XAP 7.0.2