Is it possible to change the mode from edge to relay at runtime.If a Peer A is running as an Edge then is it possible to change the mode from Edge to Relay without closing the Peer A.
Please provide me the solution.
Thanks in Advance
You can have an Edge peer become a RDV, but not a Relay. You would have to stop and restart the peer to change the behavior to Relay.
Hi n thanks fr reply,
how can i Edge peer become a RDV at runtime and why i cant change it in relay at runtime.
There is a method called setAutoStart(boolean auto) in the RendezVousService you can call to have your peer become a RDV automatically when necessary.
The reason you can't make it become a relay automatically is because no corresponding method is available.
Thanks fr reply dear, can u please tell me 1 more thing jxta is able to handle more than 3000 systems( peers) and wats the best network architecture fr it.
According to me if i am using RDV+Relay for all Public ip peers with the 1 server( supernode) then i think it works but i m not quiet sure.so please provide me the solution.
1 more thing is taht according to mike (bondolo) Message send failed error comes because of nio and socket linger and they have already correct it in latest nightly bulid and now i m using 20080910 nightly bulid but still it gives the same error with some more errors.now i m trying from myself to resolve the issue but unable to understand yet, so please tell me the what can i do to reslove this issue.
Thanks 1ce again
It does not really matter whether a RDV peer is on a public IP address or not, except for the default seeds. You should let your peers become RDV when necessary and to trust the system to work. Keep in mind that if peers can avoid going through RDV and relays, they will try to do so.
For relays, you need to make sure that some are set as seeds with a public address. You should probably use an empiric method to find the correct number. I would try ln(3000) = 8 first.
Regarding your nio issue, I would try to create a small document explaining how to replicate this issue and send it to the dev distribution list. Include error messages. Unfortunately, I am not a specialist with that, so I cannot really help you.
First of all thanks .
What is this empiric method and this will give me the minimum no. of relay for the system.Am i right?
Please tell me how can i use this empiric method ?
Another word for empiric is experiment. I mean by that you should try with 8 relays peers first and see if your system responds well overall. If this is not enough, increase the number of relays. If they are under-utilized, remove some.
Thanks adam .
Please tell how can i make my application reliable i am already using TCP .
Is it necessary to use http and any particular bandwidth is needed for a reliable connection between two Jxtasockets.
If some of your peers do not have an fix/permanent IP addresses and if they are located behind firewalls/NATs when trying to reach other peers not located behind that firewall/NAT, then you will need relays peers (i.e., http connections).
No particular bandwidth is required for a reliable connection between two JXTASockets. You just need to make sure that your router/NAT allows proper IP and HTTP traffic and that your peers are configured properly. If you want more information on this, you can find it in the book I have published (Practical JXTA).
1ce again thanks adam , please provide me the link of that book and please do tell me 1 more thing is that setAutostart(boolean auto)starts the rendezvousservice , if my peer is acting as an Edge and if i m using this method then my peer converts into Rendezvous mode.Can you please provide me the configuration file so I can understand how u r strting ur jxta and then i can compare it with my application. I am so thankful.
Thanks fr ur support.
Message was edited by: samantha001
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.