Hi, Application clusters created event is not coming to AS intermittently. But CC publishes it.
Thanks. On Mon, Mar 23, 2015 at 11:00 AM, Rajkumar Rajaratnam <[email protected]> wrote: > Hi Imesh, > > Great!. Thanks for the fix. Topology tree issue have gone now. > > Thanks. > > On Sun, Mar 22, 2015 at 9:51 PM, Imesh Gunaratne <[email protected]> wrote: > >> The above problem is now fixed, it has occurred because of complete >> applications event not being published at the time the API method was >> invoked. >> >> The startup logic is now changed as follows: >> >> 1. Start ActiveMQ manually >> 2. Start Stratos, it will first start Cloud Controller >> 3. Once Cloud Controller is activated Autoscaler will start. >> 4. Once both Cloud Controller and Autoscaler are activated Stratos >> Manager will start. >> 5. Once Stratos Manager is activated REST API will get enabled, Cloud >> Controller will publish Complete Topology event, Autoscaler will publish >> Complete Applications event, Stratos Manager will publish Complete >> Application SignUps and Complete Tenants events. >> 6. Afterwards topology, applications, application signups & tenants will >> be initialized in all components. >> >> Thanks >> >> >> On Sun, Mar 22, 2015 at 8:54 PM, Imesh Gunaratne <[email protected]> >> wrote: >> >>> Hi Raj, >>> >>> I changed the logic slightly to publish the Complete Topology event soon >>> after the Stratos Manager becomes active. This is how things happen in the >>> startup now: >>> >>> 1. Start ActiveMQ manually >>> 2. Start Stratos, it will first start Cloud Controller >>> 3. Once Cloud Controller is activated Autoscaler will start. >>> 4. Once both Cloud Controller and Autoscaler are activated Stratos >>> Manager will start. >>> 5. Once Stratos Manager is activated REST API will get enabled and Cloud >>> Controller will publish Complete Topology event. >>> 6. Afterwards topology will be initialized in all components. >>> >>> Now I cannot see any problems in the application deployment process, >>> however I can see that GET /applications/{applicationId}/runtime method is >>> returning null. It looks like the application events are not received by >>> Stratos Manager due to some reason. I'm now investigating this. >>> >>> Thanks >>> >>> On Sun, Mar 22, 2015 at 4:26 PM, Rajkumar Rajaratnam <[email protected] >>> > wrote: >>> >>>> Hi Imesh, >>>> >>>> I am still seeing this problem intermittently. When I deploy, undeploy >>>> and deploy an application again, most of the time, AS is not receiving >>>> application clusters created event. But CC is publishing it. And some parts >>>> of UI seems to be broken now. Topology tree is not displayed even after an >>>> application becomes active. Its blank. >>>> >>>> Thanks. >>>> >>>> On Sun, Mar 22, 2015 at 2:46 PM, Imesh Gunaratne <[email protected]> >>>> wrote: >>>> >>>>> I have now fixed this issue and pushed changes to master branch. The >>>>> problem was that topology was not initialized at the time >>>>> ApplicationClustersCreated event is received. >>>>> >>>>> Thanks >>>>> >>>>> On Sun, Mar 22, 2015 at 10:14 AM, Imesh Gunaratne <[email protected]> >>>>> wrote: >>>>> >>>>>> Yes looks like there is a problem in the application deployment >>>>>> process. It stops at "Application deployed successfully" and thereafter >>>>>> nothing happens. Need to debug and see what's causing this. >>>>>> >>>>>> On Sun, Mar 22, 2015 at 9:27 AM, Imesh Gunaratne <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> I cannot see any functional issues, however the integration test is >>>>>>> failing while trying to invoke the API before activating the Stratos >>>>>>> Manager. I will fix this. >>>>>>> >>>>>>> On Sun, Mar 22, 2015 at 7:49 AM, Rajkumar Rajaratnam < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi Devs, >>>>>>>> >>>>>>>> $Subject please. Even single-cartridge is not working and >>>>>>>> Integration test is also failing. >>>>>>>> >>>>>>>> Everything works fine in the following commit. >>>>>>>> >>>>>>>> commit 7cb908e3cf4ded92afc46a1792b5bf5dfac1d9b2 >>>>>>>> Author: R-Rajkumar <[email protected]> >>>>>>>> Date: Sat Mar 21 06:52:24 2015 +0530 >>>>>>>> >>>>>>>> fixing some issues with n-level-group-nesting and making a >>>>>>>> sample >>>>>>>> >>>>>>>> And some commits after this break the stuff. Will look into it. >>>>>>>> >>>>>>>> Thanks. >>>>>>>> >>>>>>>> -- >>>>>>>> Rajkumar Rajaratnam >>>>>>>> Committer & PMC Member, Apache Stratos >>>>>>>> Software Engineer, WSO2 >>>>>>>> >>>>>>>> Mobile : +94777568639 >>>>>>>> Blog : rajkumarr.com >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Imesh Gunaratne >>>>>>> >>>>>>> Technical Lead, WSO2 >>>>>>> Committer & PMC Member, Apache Stratos >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Imesh Gunaratne >>>>>> >>>>>> Technical Lead, WSO2 >>>>>> Committer & PMC Member, Apache Stratos >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Imesh Gunaratne >>>>> >>>>> Technical Lead, WSO2 >>>>> Committer & PMC Member, Apache Stratos >>>>> >>>> >>>> >>>> >>>> -- >>>> Rajkumar Rajaratnam >>>> Committer & PMC Member, Apache Stratos >>>> Software Engineer, WSO2 >>>> >>>> Mobile : +94777568639 >>>> Blog : rajkumarr.com >>>> >>> >>> >>> >>> -- >>> Imesh Gunaratne >>> >>> Technical Lead, WSO2 >>> Committer & PMC Member, Apache Stratos >>> >> >> >> >> -- >> Imesh Gunaratne >> >> Technical Lead, WSO2 >> Committer & PMC Member, Apache Stratos >> > > > > -- > Rajkumar Rajaratnam > Committer & PMC Member, Apache Stratos > Software Engineer, WSO2 > > Mobile : +94777568639 > Blog : rajkumarr.com > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com
