Skip to main content

JXME to JXME

3 replies [Last post]
galato
Offline
Joined: 2007-07-06

Hi all,

I have two JXME peers residing behind a firewall/NAT both discovering a RDV/RLY peer that is in the public domain. Once each peer discovers the PipeID of the server pipe that each one of them advertizes they both get into a loop printing the following:

RouteCM contains a record w/o any routes: jxta://[pipe id here]

If any of the two peers is a JXSE peer this problem does not occur. Has anyone else seen this one before?

Thanks

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
galato
Offline
Joined: 2007-07-06

Hey Mohamed - where can I find the midpapi20.jar that the jxme-midp2 baseline requires for compiling? None of the latest toolkits (WTK etc.) include it - not at least in this form and directory structure. I think it may be a good idea to include such dependencies in the actual project distribution don't you think?

I am still working with this issue I mentioned in this thread so if you have any insights (since you are the primary owner/developer of the project) it would be greatly appreciated. I have a feeling that this has to do with the fact that the mobile devices store routes to other peers in a slightly different way than the static peers OR the routing advs are not getting stored properly.

For crying out loud ...

galato
Offline
Joined: 2007-07-06

And shouldn't each JXME peer generate a .cache directory? That does not seem to be the case even for the default (the examples that come with the distribution) peers !! Isn't that where the routes are stored for each peer? This may be a bug in the JXME baseline ...

galato
Offline
Joined: 2007-07-06

Hi all,

I spoke with Mohamed on this issue and he concurs that most likely it is a bug in the JXME baseline.
He suggested I follow up in the code to compare JXSE with JXME and figure out why the node does
not have a route to include in the connect message. I am not too familiar with this part of the baseline
but I will still give it a shot - I know everyone is fairly busy with their own work but if anyone knows
this logic or can suggest anything to look into please let me know - I will greatly appreciate it.

The issue again is:
When trying to connect two JXME peers each of which resides behind an NATed network, they
can both find a public rendezvous, discover each other's pipes but when they try to connect to them
the spit out the following message in an infitite loop:

RouteCM contains a record w/o any routes: jxta://[pipe id here]

If one of the peers is a JXSE peer everything works fine.

Thanks again