[
https://issues.apache.org/jira/browse/BROOKLYN-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240940#comment-16240940
]
ASF GitHub Bot commented on BROOKLYN-547:
-----------------------------------------
Github user duncangrant commented on the issue:
https://github.com/apache/brooklyn-server/pull/881
Tested fairly thoroughly using a blueprint which was previously failing to
restart correctly.
> 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
>
> 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)
