You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Martin Harris (JIRA)" <ji...@apache.org> on 2015/07/28 17:12:05 UTC
[jira] [Updated] (BROOKLYN-155) Parent-level service.isUp set to
true before children are up
[ https://issues.apache.org/jira/browse/BROOKLYN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Harris updated BROOKLYN-155:
-----------------------------------
Description:
Using the following YAML, the service.isUp sensor on the parent level BasicApplication is immediately set to true, long before the service.isUp sensor on the child Tomcat entity is true
name: Basic Tomcat
location: aws-ec2:us-west-2
services:
\- type: brooklyn.entity.webapp.tomcat.TomcatServer
was:
Using the following YAML, the service.isUp sensor on the parent level BasicApplication is immediately set to true, long before the service.isUp sensor on the child Tomcat entity is true
``` YAML
name: Basic Tomcat
location: aws-ec2:us-west-2
services:
- type: brooklyn.entity.webapp.tomcat.TomcatServer
```
> Parent-level service.isUp set to true before children are up
> ------------------------------------------------------------
>
> Key: BROOKLYN-155
> URL: https://issues.apache.org/jira/browse/BROOKLYN-155
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Martin Harris
>
> Using the following YAML, the service.isUp sensor on the parent level BasicApplication is immediately set to true, long before the service.isUp sensor on the child Tomcat entity is true
> name: Basic Tomcat
> location: aws-ec2:us-west-2
> services:
> \- type: brooklyn.entity.webapp.tomcat.TomcatServer
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)