Skip to main content

problem after joining same group garbage collect

3 replies [Last post]
Joined: 2010-10-20

hi, im using jxta 2.6 with deprecated methods from 2.5
i managed both peers joining same group (jxta configuration : make one serve relay and rendezvous, 1) local ip port 9701 tcp and http port 9702 and on advanced relay rendz localip:port
2)same but in seed settings on relay and redvz set the remote computers ip:port

as a result i can see computers talk and discovering groups , joining (sometimes there is an exception on key encryption)
then when server sends queued messages the remote peer garbagecollects
then after some minutes again connection established from serverpeer and new seeding...
again garbage collect in remote peer
there is a simple lan network with a proxy server for the internet but i don't care getting peers online, just want them locally send and receive.

i think the problem is located in configuration panel, but i've never found detailed information from pc to pc lan settings logic ...

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2007-01-31

Are you trying to use the proxy mode? If yes, it has been deprecated in 2.6 and will be completely removed from 2.7. If you want to use it in 2.6, it is exactly the same method as for 2.5. We not modified the code. We have only deprecated it.


Joined: 2010-10-20

proxy if i understood well is for out of LAN communication with a peer behind a proxy, no i don't try to do that, i have both peers in same LAN network

peer(with messenger where the second peer in settings is set to connect to this one)

outputs these lines every some seconds

INFO: Line 202

Sending queued messages for net.jxta.impl.endpoint.relay.RelayServerClient@9a0db



and on the other side the second peer

INFO: Line 996 net.jxta.impl.rendezvous.rpv.PeerView.seed()

New Seeding...

Nov 9, 2010 2:33:33 PM net.jxta.logging.Logging logCheckedIn

INFO: Line 183


it seems really strange. that happens after connecting to same group (second peer normally detects the created group, but after that nothing..)

after some minutes this comes up in first :
INFO: Line 136 net.jxta.impl.endpoint.netty.NettyTransportClient.getMessenger()
processing request to open connection to tcp://
9 ═Ύί 2010 2:39:52 ΉΉ net.jxta.impl.endpoint.netty.NettyTransportClient getMesse
INFO: succeeded in connecting to tcp://
etGroup/uuid-DEADBEEFDEAFBABAFEEDBABE0000000F05/connect,3600000,keep,true, remot
e peer has logical address jxta://uuid-59616261646162614A78746150325033FDEB0AE40
9 ═Ύί 2010 2:40:00 ΉΉ net.jxta.logging.Logging logCheckedInfo

and in second one :
Failed loading seeding list from : tcp://
Nov 9, 2010 2:35:06 PM net.jxta.logging.Logging logCheckedInfo
INFO: Line 996 net.jxta.impl.rendezvous.rpv.PeerView.seed()
New Seeding...
Nov 9, 2010 2:35:06 PM net.jxta.logging.Logging logCheckedWarning
WARNING: Line 371 net.jxta.impl.util.URISeedingManager.refreshActiveSeeds()
Failed loading seeding list from : tcp://
Nov 9, 2010 2:35:17 PM net.jxta.logging.Logging logCheckedInfo
INFO: Line 183

Joined: 2007-01-31

> Failed loading seeding list from : tcp://
This often happen because people confuse addSeed() methods and addSeeding() methods in the NetworkConfigurator. One is to add the adress/URL of a seed and the other is to add the URL of a location where a list of seeds can be loaded. If you get this from Practical JXTA (first edition), make sure you have read the errata which is available with the code (c.f.