Hi, I am all for GFac registering itself with the registry. Few improvements that we could do here.
I am not sure who is calling the shutdown, i am guessing its a java shut down hook. Even if that is the case we cannot rely on this because a hard kill of the process will not trigger the shutdown hook. This will lead to GFac url left in the registry although GFac service is dead. Common technique is to use a lease. That is to associate a "valid until timestamp" with the GFac url during registration. So when GFac starts up it will register itself and say this url registration is valid for next 6 minutes and GFac is required to reregister itself with the registry ever 5 minutes or so. This way even if there is a hard kill on the GFac the url will expire and we have a safety against dangling pointer. Thanks Chathura On Tue, Sep 20, 2011 at 3:38 PM, Lahiru Gunathilake (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/AIRAVATA-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Lahiru Gunathilake closed AIRAVATA-116. > --------------------------------------- > > >> GFac url should be removed from the repo during gfac-axis2 shutdown >> ------------------------------------------------------------------- >> >> Key: AIRAVATA-116 >> URL: https://issues.apache.org/jira/browse/AIRAVATA-116 >> Project: Airavata >> Issue Type: Bug >> Reporter: Lahiru Gunathilake >> >> Ideally gfac-axis2 should remove its url from repository during the shutdown >> process. > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > -- Chathura Herath https://www.cs.indiana.edu/~cherath/ http://chathurah.blogspot.com/
