Re: [Stratos 4.1.5] [Blocker] Issues with cartridge-config.properties file

Hi, On Fri, Nov 13, 2015 at 12:42 PM, Rajkumar Rajaratnam wrote: > Hi Devs, > > This file content is as below. > > > > > > > > > > *autoscaler.service.url=https://localhost:9443/services/AutoscalerService/ > cloud.controller.service.url=https:/

[Stratos 4.1.5] [Blocker] Issues with cartridge-config.properties file

Hi Devs, This file content is as below. *autoscaler.service.url=https://localhost:9443/services/AutoscalerService/ cloud.controller.service.url=https://localhost:9443/services/CloudControllerService/

Re: [EC2] Removing the Image Id from CC Results in instances Spinning in Wrong Zones

Hi Isuru, On Wed, Nov 11, 2015 at 6:56 PM, Isuru Haththotuwa wrote: > Hi Devs, > > Noted $subject. When there is no image id in the cloud-controller.xml, the > JClouds template which is build will of default type, which does not have > any zone information. Therefore it will spin the instance in

Re: AutoscalerHealthStatEventReceiver is sleeping for 15s at startup?

+1. fine then..:) Thanks, Reka On Fri, Nov 13, 2015 at 11:09 AM, Rajkumar Rajaratnam wrote: > Hi Reka, > > Yes, that's what we are going to do. We are going to start event receiver > threads after syncing the registry with in-memory model. > > Thanks, > Raj. > > On Fri, Nov 13, 2015 at 11:06 AM

Re: AutoscalerHealthStatEventReceiver is sleeping for 15s at startup?

Hi Reka, Yes, that's what we are going to do. We are going to start event receiver threads after syncing the registry with in-memory model. Thanks, Raj. On Fri, Nov 13, 2015 at 11:06 AM, Reka Thirunavukkarasu wrote: > In that case, can't we simply start these Receiver threads atlast after > do

Re: AutoscalerHealthStatEventReceiver is sleeping for 15s at startup?

In that case, can't we simply start these Receiver threads atlast after done with all the registry loading the component activation? Thanks, Reka On Fri, Nov 13, 2015 at 11:05 AM, Rajkumar Rajaratnam wrote: > Akila, sure - will fix it. > > On Fri, Nov 13, 2015 at 11:02 AM, Akila Ravihansa Pere

Re: AutoscalerHealthStatEventReceiver is sleeping for 15s at startup?

Akila, sure - will fix it. On Fri, Nov 13, 2015 at 11:02 AM, Akila Ravihansa Perera wrote: > Thanks for the clarification Isuru! > > @Raj: will you be able to fix this as part of the fix that you are doing > to AS related to topology receiver? > > Thanks. > > On Fri, Nov 13, 2015 at 10:58 AM, Is

Re: AutoscalerHealthStatEventReceiver is sleeping for 15s at startup?

Thanks for the clarification Isuru! @Raj: will you be able to fix this as part of the fix that you are doing to AS related to topology receiver? Thanks. On Fri, Nov 13, 2015 at 10:58 AM, Isuru Haththotuwa wrote: > This can be similar to the issue Raj has explained in thread [1]. The > HealthSt

Re: AutoscalerHealthStatEventReceiver is sleeping for 15s at startup?

This can be similar to the issue Raj has explained in thread [1]. The HealthStat receiver is started before the information is loaded from the registry. We should start the HealthStat and Topology threads after loading the information from the registry. That might be the reason why we are waiting 1

Re: [Stratos 4.1.5] [Blocker] Monitors are not created on Stratos restart

On Fri, Nov 13, 2015 at 10:46 AM, Akila Ravihansa Perera wrote: > Nice catch Raj! > > I think better to wait until contexts/policies are loaded from registry > before starting AutoscalerTopologyReceiver. We're seeing this issue now > because topology is initialized immediately after starting the

Re: AutoscalerHealthStatEventReceiver is sleeping for 15s at startup?

Any thoughts please? On Wed, Nov 11, 2015 at 11:26 PM, Akila Ravihansa Perera wrote: > Hi devs, > > I noticed $subject in [1]. Is there any reason for this? As per a comment > it is waiting for Autoscaler deployer to be activated. Anyone has an idea > what this is about? > > 15s delay at the ser

Re: [Stratos 4.1.5] [Blocker] Monitors are not created on Stratos restart

Nice catch Raj! I think better to wait until contexts/policies are loaded from registry before starting AutoscalerTopologyReceiver. We're seeing this issue now because topology is initialized immediately after starting the receiver with topology initializing optimization. Thanks. On Fri, Nov 13,

[Stratos 4.1.5] [Blocker] Monitors are not created on Stratos restart

Hi Devs, Experiencing $Subject. Root cause is, AS received the complete-topology-event before loading application-contexts from registry to in-memory model. So the complete-topology-event is ignored by AS, but the topology is initialized. This also means that all the upcoming periodic complete-to

Re: PCA live test is failing

Yes. That would be better. Otherwise it would be hard to find the root cause when tests are failing. On Thu, Nov 12, 2015 at 9:16 PM, Akila Ravihansa Perera wrote: > Great work Pubudu! > > Shall we enforce a min count for thread pool size in messaging event > receivers? This will avoid mistakenl

Jenkins build is back to stable : Stratos-41x-Nightly-Build » Apache Stratos - Messaging #48

See

Jenkins build is back to stable : Stratos-41x-Nightly-Build #48

See

[GitHub] stratos pull request: Renaming dashboards and updating ues-patch t...

Github user Thanu closed the pull request at: https://github.com/apache/stratos/pull/490 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] stratos pull request: Renaming dashboards and updating ues-patch t...

Github user Thanu commented on the pull request: https://github.com/apache/stratos/pull/490#issuecomment-156146324 Merged with commit 12110f4b83b3f40a487808a386312137e167e5d7, 30c2c6abd1327d3f400d46d569b86acf253efd5a, 4862019c4a2979565d75ed8fb674bc3704cac21f and b67418df9919e0caf79eb

Re: PCA live test is failing

Great work Pubudu! Shall we enforce a min count for thread pool size in messaging event receivers? This will avoid mistakenly setting a value that is too low to handle the load. On Thu, Nov 12, 2015 at 4:08 PM, Isuru Haththotuwa wrote: > > > On Thu, Nov 12, 2015 at 3:54 PM, Pubudu Gunatilaka >

Re: [Dev] Publishing Complete Topology event on Demand

Great work Akila! This is definitely a tremendous improvement. On Wed, Nov 11, 2015 at 3:27 PM, Akila Ravihansa Perera wrote: > Hi, > > I've implemented the following improvements and merged in [1]. JIRAs > created [2, 3, 4] to track these tasks. > > - On-demand initialization of complete topol

Re: PCA live test is failing

On Thu, Nov 12, 2015 at 3:54 PM, Pubudu Gunatilaka wrote: > PCA live tests were failing due to not having enough threads in the thread > pool. It is not the CEP HA mode test case but the agent startup test case > which was failing as it was waiting for the complete topology event to > receive. Th

Re: PCA live test is failing

PCA live tests were failing due to not having enough threads in the thread pool. It is not the CEP HA mode test case but the agent startup test case which was failing as it was waiting for the complete topology event to receive. The event listener could not be started due to lack of threads. I inc

[jira] [Assigned] (STRATOS-1597) Auth token generation admin user name should be in configuration

[ https://issues.apache.org/jira/browse/STRATOS-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gayan Gunarathne reassigned STRATOS-1597: - Assignee: Gayan Gunarathne (was: Udara Liyanage) > Auth token generation admin

[jira] [Resolved] (STRATOS-1597) Auth token generation admin user name should be in configuration

[ https://issues.apache.org/jira/browse/STRATOS-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gayan Gunarathne resolved STRATOS-1597. --- Resolution: Fixed Fixed with adc8576adfff1ef2cd09d8058259dd59600de000 > Auth token