Failure to resolve output pipe

Alex Iribarren <[email protected]> Tue, 12 Jul 2005 16:30:32 +0000 (UTC)
Newsgroups gmane.comp.java.jxta.user,gmane.comp.java.jxta.devel
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I've been noticing this for a while, and I've finally decided to
ask. I have several peers running on the same machine and they
behave just like they're supposed to, except that sometimes they
can't resolve each other's pipes in time.

I'm using something like:
OutputPipe outPipe =
netPeerGroup.getPipeService().createOutputPipe(pipeAdv,
Params.PIPE_TIMEOUT*1000);

where PIPE_TIMEOUT = 10. This sometimes causes a IOException, which
if I read the API correctly means the pipe couldn't be resolved,
meaning that the owner of the pipe advertised in pipeAdv could not
be found. I remember somebody saying in [email protected] that in their
tests a message took up to 19 seconds to be sent between different
peers through the Internet. Surely 10 seconds is enough to resolve a
pipe within my own machine, is it not?

Is this normal? Does it happen to anyone else?

Regards,
Alex
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDlxsSos7l8uF4XVERApgjAKCps1JXHgNNJqaDYa1BFenvf3VMAgCfRQaB
Fs0k9Rx0AFiZjkNtc20WX3E=
=d/M6
-----END PGP SIGNATURE-----