Re: plz help.... rendezvous discovery in a subnet

Hi Suresh,

I guess there are a couple of other questions that would help:

- are you using the default netPeerGroup, or a private one?
- can the machines on your subnet reach the Internet, or is the  
subnet isolated?
- is multicast enabled?

It sounds as if there is no reachable RDV in the netPeerGroup for  
Machine 2 to find (and possibly for Machine 1 to publish to). A  
netPeerGroup RDV is required to discover the group. (I can't recall  
whether multicast removes the need for a RDV in the case of nodes on  
the same subnet. I should know that, but I'm all foggy today, sorry :-b)

If you are using the public/default netPeerGroup, you might try not  
removing the seeding rdvs in the configurator. If you're using a  
private (or just isolated by network topology) netPeerGroup, you  
could ensure that machine 1 becomes a netPeerGroup RDV by setting the  
option in the configurator dialog (or you could do it  
programmatically, as well). At any rate, try to determine whether  
machine 2 is connected to a netPeerGroup RDV before trying to  
discover the new group. I think rdvservice.isConnectedToRendezvous()  
(or something like that) will tell you yes or no.

It's still a little too ambiguous to say why it works when both are  
on the same machine. A little more info/experimentation should help  
solve the mystery.

Good luck,

Vanessa

On 26-Sep-05, at 2:45 PM, Anamanamuri, Suresh wrote:

> Hi Vanessa,
>
>
>
> A million thanks for the reply.
>
>
>
> This is what we are doing…
>
>
>
> We have two machines on the same subnet (linux)…
>
>
>
> Machine 1, creates a group “suresh” in netPeerGroup, publishes the  
> “suresh” group advertisement in netPeerGroup, and then joins this  
> group “suresh” . Rendezvous service is obtained from “suresh” group  
> and using this service machine 1 becomes a rendezvous…
>
>
>
> Machine 2, tries to discover “suresh” group, using group id, in  
> netPeerGroup (using a name, attribute based search from  
> advertisements obtained). It looks for both local and remote  
> advertisements continuously until the group by name “suresh” is  
> found at 1 second interval.
>
>
>
> Our problem is that machine 2 never discovers the group “suresh”  
> and thus the correct rendezvous.
>
>
>
> However, when we simulated machine 1 and machine 2 on the same  
> computer, but in different sub directories… everything worked  
> perfectly and beautifully…
>
>
>
> We didn’t use any configurator of our own… When we executed the  
> programs, the pop-up GUI was used to select options… In GUI  
> configurator, we disabled HTTP settings (in Advanced tab), and  
> removed the default seeding rendezvous (from Rendezvous/Relays tab)…
>
>
>
> The only thing that confounds us, is the fact that the programs run  
> as desired when the programs are executed on the same machine with  
> same configuration… However, the communication just doesn’t happen  
> when the programs are run on different machines…
>
>
>
> Any help is greatly appreciated
>
>
>
>
>
> Thank you,
>
> Suresh Anamanamuri.
>
> From: Vanessa Williams [mailto:[email protected]]
> Sent: Saturday, September 24, 2005 4:13 PM
> To: [email protected]
> Subject: Re: [JXTA user] plz help.... rendezvous discovery in a subnet
>
>
>
> Hi Suresh,
>
>
>
> unfortunately, there isn't enough information in your message to  
> really help you. However, if the code works when both the rdv and  
> discovering peer are on the same machine, it's most likely the  
> configuration of the peers that is causing the problem. Can you  
> provide more details about the configuration of the two peers?  
> Also, did you use the default configurator or the ext/config  
> package--and if the latter, which profile(s) did you use?
>
>
>
> Cheers,
>
>
>
> Vanessa
>
>
>
> On 23-Sep-05, at 5:47 PM, Anamanamuri, Suresh wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thanks,
>
> Suresh Anamanamuri.
>
>
>
>
>
>
>
>
>