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

Posted to dev@felix.apache.org by "Timothy Ward (JIRA)" <ji...@apache.org> on 2016/05/03 18:23:12 UTC

[jira] [Created] (FELIX-5248) SCR does not reactivate a failed component after a configuration update

Timothy Ward created FELIX-5248:
-----------------------------------

             Summary: SCR does not reactivate a failed component after a configuration update
                 Key: FELIX-5248
                 URL: https://issues.apache.org/jira/browse/FELIX-5248
             Project: Felix
          Issue Type: Bug
          Components: Declarative Services (SCR)
    Affects Versions: scr-2.0.4
            Reporter: Timothy Ward
            Priority: Blocker


A configurable SCR component may fail to activate by throwing an exception if the factory configuration contains bad values. If the factory configuration for that component is then updated SCR should attempt to recreate and activate the component. Instead the component sits in the "satisfied" state forever, and updates to the factory configuration are ignored.

This makes it impossible to "fix" a mistaken configuration without deleting and recreating it.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)