edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (EDGENT-397) IotProvider doesn't restart failed applications
Date Tue, 14 Mar 2017 21:11:41 GMT

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

Dale LaBossiere updated EDGENT-397:
-----------------------------------
    Issue Type: New Feature  (was: Bug)

> IotProvider doesn't restart failed applications
> -----------------------------------------------
>
>                 Key: EDGENT-397
>                 URL: https://issues.apache.org/jira/browse/EDGENT-397
>             Project: Edgent
>          Issue Type: New Feature
>          Components: Providers
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>
> IotProvider includes the JobMonitorApp.  JobMonitorApp requires that a JobRegistryService
is registered in order to receive job status events.
> Neither IotProvider nor anything else is registering a JobRegistryService so the jobs
aren't being restarted when using the IotProvider.
> Note, JobMonitorAppTest verifies the app in isolation however there isn't an analogous
test in an IotProvider context.
> See also EDGENT-396 and EDGENT-112



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

Mime
View raw message