You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Aled Sage (JIRA)" <ji...@apache.org> on 2017/04/06 12:13:41 UTC

[jira] [Created] (BROOKLYN-468) restart effector does not restart the entity's feeds

Aled Sage created BROOKLYN-468:
----------------------------------

             Summary: restart effector does not restart the entity's feeds
                 Key: BROOKLYN-468
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-468
             Project: Brooklyn
          Issue Type: Bug
    Affects Versions: 0.10.0
            Reporter: Aled Sage


I have a yaml-based {{VanillaSoftwareProcess}}. I called its {{restart}} effector. This caused its feeds to be stopped, and not restarted (as visible via the Groovy console:

{noformat}
mgmt.getEntityManager().getEntity("qafop4hk6f").feeds().getFeeds()

[HttpFeed{uniqueTag=HttpFeed[http[service.isHealthy]], running=false, entity=VanillaSoftwareProcessImpl{id=qafop4hk6f}, id=gt1wzcfb2r}, HttpFeed{uniqueTag=HttpFeed[http[service.status]], running=false, entity=VanillaSoftwareProcessImpl{id=qafop4hk6f}, id=u2dx5wkii7}]
{noformat}

IMO, when the entity restarts the feeds should be automatically restarted.

The same applies if you call {{stop}} and then later call {{start}}.

One tricky thing is we don't know which feeds were actually running before {{stop}} was called - should we start all the feeds? Or should we record which feeds we've automatically stopped, so we know which ones to start? (For the latter, that could prove tricky if Brooklyn is restarted - we'd need to persist it, which gets annoying.)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)