Skip to main content

Public rendezvous available?

11 replies [Last post]
hruben
Offline
Joined: 2007-03-29
Points: 0

Hello,

I want to use JXTA for my diploma thesis, but find it very hard to get started. I've been experimenting with several applications for a while (Shell, JxtaView, MyJxta, jxCube, ...) but I never managed to discover peers on the internet (I did on local networks, however). Now, I think I've found the reason:

I am behind a firewall and NAT router, so I need to use http to find any rendezvous peers on the internet, right? However, looking at the pubnet list produced by http://rdv.jxtahosts.net/cgi-bin/rendezvous.cgi?2, there is only one http rendezvous server available, http://209.128.126.120 ("pelican"). When I try to ping it, I get no response, so I guess this server is down.

When TCP doesn't work and the only public http server is unreachable, it is pretty obvious I can't find any peers on the internet. Am I right?

My two questions are:
- is it true that 209.128.126.120 is down?
- is there any other public rendezvous peer I can use?

(a third question could be: If it's down, why is it still on the seeding list, but that is not important to me)

TIA
--Helge.

P. S. chrisdekock put a very similar question in the thread "is jxta a dead cat" today. But as an answer is very important to me, I decided to make it a separate thread.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
cuttlazz
Offline
Joined: 2007-04-12
Points: 0

Hi hruben!
I've finnally did it! :D. I have configured it manually launching the
jxta shell first, located in net.jxta.impl.peergroup.Boot.
then i launch myjxta and everithing runs well.(excepting video calls, lol) .

I agree with you when you say the public rendezvous servers are overloded.
However i think, JXTA group should provide more servers in way to facilitate new
users to use JXTA easaly! run JXTA demo apps helps to understand how P2P work
and realize JXTA capabilites!

Thanks

Regards

Claudio

adamman71
Offline
Joined: 2007-01-31
Points: 0

Hi,

Unfortunately, the http://rdv.jxtahosts.net/cgi-bin/rendezvous.cgi?2 peers have not been maintained. So there is not public rdv that I know of.

Firewalls applications on PC can silently block communication, even in a LAN. Vista is known to silently kill multicast communication... I took me day to find out...

If you are on a LAN, try disactivating firewalls on your devices, then things should go fine...

J.

kapitanpieklo
Offline
Joined: 2010-01-27
Points: 0

Hi,

hruben could you give me more information about configuration of MyJxta you have used in order to find peers on LAN?

I've tried MyJxta 2.4.1 and 2.3.1 with default settings (configuration manager doesn't start even with the first execution) and the peers cannot find each other. I have two hosts connected to the same LAN (without WAN), firewalls are disabled.

Please help.

chrisdekock
Offline
Joined: 2007-03-07
Points: 0

Hi hruben,

[b]is it true that 209.128.126.120 is down?[/b]

Probably not. The server seems to be set up to not reply to ICMP requests i.e PING. Rather try and see if you can Telnet onto the server on the given ports:

TELNET 209.128.126.120 9700
and
TELNET 209.128.126.120 9710

Don't get too excited though, even if you can telnet onto that port, you might not be able to get your programs working on the PubNet.

[b]is there any other public rendezvous peer I can use?[/b]

I was wondering that myself. I know the PubNet is flooded and we should develop on a LAN setup, but how you eventually get your app working on the internet I'm not sure. Do I have to create my own "super" rendezvous to which my user's apps connect or can I rely on the PubNet for my initial rendezvous?

I've read on some blog or thread somewhere that there are other public rendezvous.
Could someone please provide a list?

PS. You mention, you "find it very hard to get started". I've seen so many threads asking:
"Why cant I discover any peers"
"rdvstatus shows nothing"
"peers -r doesn't work"
"Can't get basic examples to work"
This is really not good news for a technology with so much potential. It shows how many developers are interested in JXTA but can't get started. The JXTA shell is supposed to be a springboard into the technology, but as the first step you take relies on the shaky PubNet, many might decide to turn back. I will however press on and I hope you will too.

Message was edited by: chrisdekock

hruben
Offline
Joined: 2007-03-29
Points: 0

Hi chrisdekock,

thanks for your reply. I have tried telnet before, but 209.128.126.120 did not reply. And I read earlier somewhere, that rendezvous peers should reply to ICMP requests.
But anyway, what I wanted to know is why that server is unreachable. Is it because of my personal network setup or is it because the server doesn't reply. Your post answered that question. Whether it is down or "just" overloaded, doesn't make a difference. In all my attempts, it was unreachable.

I totally agree with what you say about developers being kept away from JXTA by the non-working Pubnet. It has taken me a long time of investigation to come to the conclusion that it is not my personal fault that I can't find any peers. No matter what application I tried, they all use the same seeding URLs, and so, none of them showed any other peer. And all threads I have found in this forum regarding this topic remained unanswered. A less enthusiastic developer would have given up a lot earlier.

As I see it now, my only way out is to set up my own rendezvous server. I am just a student working on my diploma thesis, however, and I don't think I have the means to. I need my application to run on the internet, not just in a LAN. But like you, I have not given up. Yet.

So, I, too, would highly appreciate a list of alternative seeding URLs or rendezvous peers! If anyone can help, please give us a hint.

I would also appreciate the online tutorials and documentation being updated to make it clear that the pubnet tends to be overloaded and is not reliable.

--H.

cuttlazz
Offline
Joined: 2007-04-12
Points: 0

hi!

I did my thesis too, with JXTA 2.0, in 2004.
I was faced with the problems mainly related to jxta versions,
because i had docs related to versions 1.x, with stuf that didn't
worked in jxta 2.0. I've passed hard times :s!!!
However i did it!
I've tried to download now myJXTA 2.4.1, i cannot put it working,
even in a lan or in the internet. It is now not so flexible that in 2004.
i don't understand why!!!! The rendezvous doesn't answer!!!! I enter
in automatic rendezvous, and nothing happens! i cannot find other peers.
by the way my old applications steel working today, under JRE 1.4.x, but working well.
I also aggree that a so powerfull technology is so hard to try by begginers. it
may get frustrated and give up!!!!

hruben
Offline
Joined: 2007-03-29
Points: 0

Hi cuttlazz,

like chrisdekock said, you won't get myJXTA to work with the default public rendezvous servers, because they are all overloaded. I did get myJXTA to work in a LAN, however. You need to configure one of the peers to act as a rendezvous.
I managed to get the 'turnkey JXTA demo' to run in a LAN, too (see http://www.petrovic.org/blog/2006/11/15/a-turnkey-private-jxta-net-demo/ ). My JXTA-lib did not match the expected path, so I had to change build.xml, but in the end, I got it running. I will use it as a starting point for my own app now.

--Helge.

learning_jxta
Offline
Joined: 2007-03-21
Points: 0

Hello hruben,

I downlaoded this application. But there are some errors when I compiled it with ant even though I have modified the build.xml file. Could you please tell me how you compiled it?

The following is the build.xml I used. It always says there is an error:

BUILD FAILED
C:\JXTA\PrivateNet\build.xml:50: Error running javac.exe compiler

Thanks in advance!

//////////////////////////////



















































hruben
Offline
Joined: 2007-03-29
Points: 0

Hello,

you changed the source path from "src" to "privatenet/privatenet". I didn't change the source path, however, but the platform path. The only (as far as I remember) change I made to the build.xml file was changing this:

[b]
[/b]

to

[b]
[/b]

where ./JXTA is my JXTA directory, which contains the /lib subdirectory with jxta.jar and other stuff.

You should restore the original build.xml file before trying this to make sure there are no other changes you forgot about.

HTH

--Helge.

learning_jxta
Offline
Joined: 2007-03-21
Points: 0

Hello Hruben,

Thank you for your reply. But there is still some problem when I restored to original build.xml. Actually I downloaded it again and unzipped it.

Firstly there problem is:
C:\JXTA\PrivateNet_1\build.xml:50: C:\JXTA\PrivateNet_1\JXTA\jnlp\lib not found.

I created a sub folder and copied the lib files into C:\JXTA\PrivateNet_1\JXTA\jnlp\lib.

Then I built it again. The problem is:

BUILD FAILED
C:\JXTA\PrivateNet_1\build.xml:50: Error running javac.exe compiler

The line in the build.xml is:

hruben
Offline
Joined: 2007-03-29
Points: 0

Hello,

sorry, but I never had this kind of problem and I can't give you good advice. I would guess it has something to do with the Java compiler not being found and possibly your Ant configuration. You obviously work under Windows, so do I. I used Ant which ships with Eclipse 3.2. On the DOS prompt, I changed to the privatenet directory and entered

[b]c:\eclipse\plugins\org.apache.ant_1.6.5\bin\ant node[/b]

I have never worked with Ant before, so I am probably not the right person to ask.

Good luck!

--Helge.