I have now fixed this issue by publishing the Complete Topology event at the Cloud Controller startup. Now the server is usable as soon as it prints the managerment console URL.
The problem was that the topology synchronizer task was not running initially when its scheduled. Thanks On Fri, Feb 6, 2015 at 6:30 AM, Isuru Haththotuwa <[email protected]> wrote: > IMHO the simplest strategy to tackle this is to add a check to SM (at the > rest endpoint) and in the other components (CC, AS) where necessary to find > whether the topology has been properly initialized. > > On Fri, Feb 6, 2015 at 1:30 AM, Reka Thirunavukkarasu <[email protected]> > wrote: > >> Thanks Gayan for the information.. >> >> Yah Imesh..It seems that it is there from the beginning.. >> >> Thanks, >> Reka >> >> >> On Wed, Feb 4, 2015 at 6:50 AM, Imesh Gunaratne <[email protected]> wrote: >> >>> Hi Reka, >>> >>> According to my understanding this problem was there from the begining. >>> I will investigate and see what's causing it. >>> >>> Thanks >>> >>> On Tue, Feb 3, 2015 at 5:00 PM, Gayan Gunarathne <[email protected]> >>> wrote: >>> >>>> Hi Reka, >>>> >>>> This is happen when server started. Even the server started we can't >>>> deploy the application until the complete topology event received. >>>> (Topology get initialized with the complete topology event.) >>>> >>>> We come across this when doing the integration testing. Integration >>>> test execution will start once the server started. But the application >>>> deployment get failed if this test execution happen before complete >>>> topology is received.So we need to wait until for the complete topology >>>> event to execute the test suite. >>>> >>>> Thanks, >>>> Gayan >>>> >>>> >>>> On Tue, Feb 3, 2015 at 12:59 AM, Reka Thirunavukkarasu <[email protected]> >>>> wrote: >>>> >>>>> Hi Gayan, >>>>> >>>>> Can you explain me the current application deployment model and the >>>>> persistence model? AFAIR, in order to handle this kind of scenario, the >>>>> relevant implementation has been added in pre-alpha. I will check and >>>>> verify it.. >>>>> >>>>> Thanks, >>>>> Reka >>>>> >>>>> On Mon, Feb 2, 2015 at 12:19 PM, Gayan Gunarathne <[email protected]> >>>>> wrote: >>>>> >>>>>> AFAIU Topology manager get initialized after only the complete >>>>>> topology event is received.Application deployment is getting fail if the >>>>>> topology in not initialized. >>>>>> >>>>>> IMO there will be two options. >>>>>> 1. Block the outside interfaces (such as rest api, CLI ) until the >>>>>> topology initialize. >>>>>> If we use this our integration test execution should wait until >>>>>> the complete topology event received. >>>>>> 2. We can delay the server start(wait in the main thread) until the >>>>>> topology get initialized. >>>>>> >>>>>> WDYT? >>>>>> >>>>>> Thanks, >>>>>> Gayan >>>>>> >>>>>> On Mon, Feb 2, 2015 at 8:18 PM, Imesh Gunaratne <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hi Devs, >>>>>>> >>>>>>> It seems like if we deploy an application before Complete Topology >>>>>>> event is received, application monitor does not get created. As a result >>>>>>> application is not created. >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Imesh Gunaratne >>>>>>> >>>>>>> Technical Lead, WSO2 >>>>>>> Committer & PMC Member, Apache Stratos >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Gayan Gunarathne >>>>>> Technical Lead >>>>>> WSO2 Inc. (http://wso2.com) >>>>>> email : [email protected] | mobile : +94 766819985 >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Reka Thirunavukkarasu >>>>> Senior Software Engineer, >>>>> WSO2, Inc.:http://wso2.com, >>>>> Mobile: +94776442007 >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Gayan Gunarathne >>>> Technical Lead >>>> WSO2 Inc. (http://wso2.com) >>>> email : [email protected] | mobile : +94 766819985 >>>> >>>> >>> >>> >>> >>> -- >>> Imesh Gunaratne >>> >>> Technical Lead, WSO2 >>> Committer & PMC Member, Apache Stratos >>> >> >> >> >> -- >> Reka Thirunavukkarasu >> Senior Software Engineer, >> WSO2, Inc.:http://wso2.com, >> Mobile: >> +94776442007 >> >> -- >> <%2B94776442007> >> <%2B94776442007> >> Thanks and Regards, >> >> Isuru H. >> <%2B94776442007> >> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>* >> >> >> * <http://wso2.com/>* >> >> >> -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
