[jira] [Resolved] (BROOKLYN-547) VanillaSoftwareProcess.restart fails if sshMonitoring disabled

["Aled Sage (JIRA)" <ji...@apache.org>]

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

Aled Sage resolved BROOKLYN-547.
--------------------------------
    Resolution: Fixed
      Assignee: Aled Sage

(Introduced after 0.12.0 was released, and fixed before 1.0.0 was released - i.e. only ever affected snapshot. See https://github.com/apache/brooklyn-server/blob/rel/apache-brooklyn-0.12.0/software/base/src/main/java/org/apache/brooklyn/entity/software/base/VanillaSoftwareProcessImpl.java#L28-L31).

> VanillaSoftwareProcess.restart fails if sshMonitoring disabled
> --------------------------------------------------------------
>
>                 Key: BROOKLYN-547
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-547
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Aled Sage
>            Assignee: Aled Sage
>
> When using {{VanillaSoftwareProcess}} with {{sshMonitoring.enabled: false}}, the entity is set on fire if you call the {{restart}} effector.
> This is because... when the entity transitions to service.isUp=false during the restart, it triggers the enricher {{UpdatingNotUpFromServiceProcessIsRunning}}, which populates the service-not-up-indicator with {{service.process.isRunning}}. This is never cleared because we are not polling over ssh for the check-running.
> A solution would be to remove this enricher in {{VanillaSoftwareProcess}}, if ssh-monitoring is disabled.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)