You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@edgent.apache.org by "Dale LaBossiere (JIRA)" <ji...@apache.org> on 2017/02/02 16:54:51 UTC

[jira] [Resolved] (EDGENT-374) IotProvider edgentControl commands are silent no-ops under some failure conditions

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

Dale LaBossiere resolved EDGENT-374.
------------------------------------
    Resolution: Fixed

resolved via https://github.com/apache/incubator-edgent/pull/279

> IotProvider edgentControl commands are silent no-ops under some failure conditions
> ----------------------------------------------------------------------------------
>
>                 Key: EDGENT-374
>                 URL: https://issues.apache.org/jira/browse/EDGENT-374
>             Project: Edgent
>          Issue Type: Bug
>          Components: Providers
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>            Priority: Minor
>
> Sending an IotProvider app an edgentControl command request is a silent no-op under at least these conditions:
> - unable to locate the specified MXBean service - e.g., due to misspelt name or alias)
> - unable to locate the Method for the bean - e.g., due to misspelt method name, wrong number or args specified
> Seems like JsonControlService.controlOperation() should log an error or at least a warn for these cases.



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