Skip to main content

Finding pipes and connectivity

1 reply [Last post]
galato
Offline
Joined: 2007-07-06
Points: 0

I have 2 peers each publishing a server pipe with a rdv/rly and then looking for each other's server pipe on that rdv/rly and connect to it each with a client pipe. Funny enough, if I modify the code for one of the peers only to publish a server pipe and not look for any pipes in the rdv/rly, and the other peer to find it the published pipe and connect to it, the connectivity fails - yes just like you would say, it makes no sense to me either - has anyone seen this behavior before? Why if both peers publish server pipes and each connect to them with client pipes the connectivity is just fine? Is this a routing issue? Thanks

WARNING: Failed to connect to address :jxta://uuid-59616261646162614E50472050325033D796EAA4B1CB4FA193E6F549FA10E82703
Jun 23, 2010 3:59:31 PM net.jxta.impl.resolver.ResolverServiceImpl sendMessage
WARNING: Failed to add route for urn:jxta:uuid-59616261646162614E50472050325033D796EAA4B1CB4FA193E6F549FA10E82703
Jun 23, 2010 3:59:31 PM net.jxta.impl.resolver.ResolverServiceImpl$FailureListener messageSendFailed
WARNING: Clearing SRDI tables for failed peer : urn:jxta:uuid-59616261646162614E50472050325033D796EAA4B1CB4FA193E6F549FA10E82703

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
Points: 0

Also I noticed that if I start the rdv/rly (super peer) to accept connections on ports 9501 and 9502 respectively using tcp and tcp as transports, a telnet to 9501 port responds happily with the JXTAHELLO, but the connection to 9502 is refused. Is this normal for the relay functionality of the super peer??

Thanks