stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anuruddha Premalal (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (STRATOS-1487) Cluster Monitors were not created because CompleteTopologyEvent was published before AutoscalerComponent was activated
Date Mon, 03 Aug 2015 10:48:04 GMT

     [ https://issues.apache.org/jira/browse/STRATOS-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anuruddha Premalal resolved STRATOS-1487.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s: 4.1.0
                   4.1.0 M1

This was already fixed. Adding -Dstratos.component.startup.synchronizer.enabled=true to stratos.sh
resolved the issue.

> Cluster Monitors were not created because CompleteTopologyEvent was published before
AutoscalerComponent was activated
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: STRATOS-1487
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1487
>             Project: Stratos
>          Issue Type: Bug
>    Affects Versions: 4.1.0 Beta2
>            Reporter: Anuruddha Premalal
>             Fix For: 4.1.0 M1, 4.1.0
>
>         Attachments: wso2carbon.log
>
>
> Line number 478 - CompleteTopologyEvent was received by AS
> Line number 501 - AutoscalerComponent was activated
> When AS received CompleteTopologyEvent, it didn't load the application context from registry.
Hence it just logged "The application is not yet deployed for this [application] asdevelopment"
(Line number 482) and ignored the CompleteTopologyEvent. And CompleteTopologyEvent is published
only once (until topology is initialized) - so there is no way that the monitors will be created.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message