[Smartfrog.org-JIRA] Commented: (SFOS-5) Smartfrog is brittle against multiple hosts systems

    [ http://jira.smartfrog.org/browse/SFOS-5?page=comments#action_10013 ] 
            
Julio Guijarro commented on SFOS-5:
-----------------------------------

> 1. as a network moves around, any running sf daemon gets into trouble when the network address changes. You 
> cannot talk to it any more, which means there is no way to shut it down cleanly. 
Of course, the network address changed so unless you use autodiscovery you won't be able to find where it is anymore.
Also, RMI has problems with Laptops and only Sun can change that.

> 2. We need a way to talk to a daemon on localhost, regardless of which other ports it is on. 
You could use multicals or SLP to always now where it is. It is not the default behaviour because of the multicasting traffic. We chould also use the new REST api, but again is an overhead that should only be used when it is needed.

>3. We need a way to tell a daemon to re-bind to the network ports. This may be something that RMI prevents us. 
See one. RMI is a big problem here. But I will see if I can improve its behaviour.

>4. We need to remove references to java.net.InetAddress.getLocalHost() in the code, and isolate all hostname work >into a single module which we can manage better. 
TODO - subtask opened.

>5. When choosing which ports to listen to, we should recognise self-assigned IPv4 addresses (169.*) and give them >lowest priority. 
You can decide witch interface you want to use.
Modify: SFSERVERHOSTNAME environment variable and you can select the NIC that SF will use. To limit the communication ports for a component add the attribute: with an integer or vector of integers.


> Smartfrog is brittle against multiple hosts systems
> ---------------------------------------------------
>
>                 Key: SFOS-5
>                 URL: http://jira.smartfrog.org/browse/SFOS-5
>             Project: SmartFrog
>          Issue Type: Bug
>          Components: .sfCore
>    Affects Versions: 3.10.000
>         Environment: laptops with Wifi and VmWare networks
>            Reporter: Steve Loughran
>         Assigned To: Julio Guijarro
>
> 1. as a network moves around, any running sf daemon gets into trouble when the network address changes. You cannot talk to it any more, which means there is no way to shut it down cleanly.
> 2. We need a way to talk to a daemon on localhost, regardless of which other ports it is on. 
> 3. We need a way to tell a daemon to re-bind to the network ports. This may be something that RMI prevents us.
> 4. We need to remove references to java.net.InetAddress.getLocalHost() in the code, and isolate all hostname work into a single module which we can manage better. 
> 5. When choosing which ports to listen to, we should recognise self-assigned IPv4 addresses (169.*) and give them lowest priority.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.smartfrog.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV