Skip to main content

RDV/Router not working in Peer Group?

1 reply [Last post]
kevamc
Offline
Joined: 2007-06-27
Points: 0

Hi,

I am relatively new to JXTA and have a problem configuring it to work across subnets. I am really stuck with this problem and it is eroding my confidence in my ability to construct a working JXTA application. If anyone can help, I would be really grateful. Here goes:

I have 2 networks (LIVE and TEST) in my office with 2 peers in each:

• LIVE
- Dell71
- Dell74
• TEST
- Dell150
- Dell151

There is a router between the two networks.

I am testing my network connectivity using the Shell application. Machine Dell150 is configured to run the shell as a Rendezvous and Router. Machines Dell71, Dell74 and Dell151 are configured as EDGE shell applications that ONLY use machine Dell150 as a Rendezvous. [PlatformConfig for EDGE peer attached].

I can see that the EDGE peers use Dell150 as both Rendezvous and Relay:

JXTA>rdvstatus

Rendezvous Status:
__________________

Current configuration : EDGE
"dell71" A p t [3955/1035]

Peer View :
"JXTA.ORG:38" A P t [3483/3243]
"dell150" A P t [3952/1035]
"JXTA.ORG:36" A P t [3705/3705]
"JXTA.ORG:37" A P t [3935/3701]

Rendezvous Connections :
dell150 C : 1089854 / 789854

Rendezvous Disconnections :
[None]

When the EDGE peers start up, they can see the rendezvous. If I create a new group (iqlab) then all machines can see that group. If I try and use the shell TALK command, then all peers can send messages to each other. In other words, all works as expected.

(NOTE: at this stage, a query for peers does not return all peers connected to the rendezvous e.g. typing peers –r on Dell71 does not show Dell74 or Dell151 as peers but does show the rendezvous peer Dell151 as a peer. Is this right?)

However, when the peers join the new peer group, things start to go wrong. If I use the TALK application within the new peer group, I get mixed results. Machines Dell151 and Dell150 can use TALK to exchange messages but machines Dell71 and Dell74 cannot exchange messages with anyone. It is like they are no longer aware of the Rendezvous. This might not be far from the truth because when you type rdvstatus while in the new peer group, it indicates that there is no connection to the rendezvous server:

JXTA>whoami -g
NetPeerGroup
default Net Peer Group
urn:jxta:jxta-NetGroup
JXTA>rdvstatus

Rendezvous Status:
__________________

Current configuration : EDGE
"dell71" A p t [6733/866]

Peer View :
"JXTA.ORG:38" A P t [6261/6021]
"dell150" A P t [6730/751]
"JXTA.ORG:36" A P t [6483/6483]
"JXTA.ORG:37" A P t [6713/2278]

Rendezvous Connections :
dell150 C : 333232 / 33232

Rendezvous Disconnections :
[None]

JXTA>groups
group0: name = iqlab
JXTA>join -d group0
dell71 - Enter the identity you want to use for group 'iqlab' :
Identity : eee
JXTA>rdvstatus

Rendezvous Status:
__________________

Current configuration : EDGE
"dell71" A p t [6/6]

Peer View :
[None]

Rendezvous Connections :
[None]

Rendezvous Disconnections :
[None]

Is there something that I am missing here. Do you have to specify Router/Rendezvous information on a per-peer-group basis?

In addition, I am having a hard time getting useful debug information out of JXTA. Full debugging outputs so much info that I cannot determine anything useful. Does anyone know a good log4j configuration that outputs sufficient information for tracking down connectivity issues between peers?

Many thanks for any help that people can offer.

Kevin.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
thenetworker
Offline
Joined: 2003-06-13
Points: 0

I suggest you just write some simple code to test your scenario. You don't have to spend a lot of time to understand the Shell, which has extra conceptual weight in it. It is much easier for you to use JXTA API.