[ 
https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869987#comment-15869987
 ] 

Alex Soto commented on FELIX-5549:
----------------------------------

To clarify:  I expect the FactoryComp to be deactivated and activated again 
when the configuration changes.  From the log file, you can see the different 
states of the component:

{quote}2017-02-16 08:54:01,697 | INFO  | pool-2-thread-1  | FactoryComp         
             | 11 - org.alex.soto.blueprint-ds-config-reload - 0.0.1.SNAPSHOT | 
Activated FactoryComp
2017-02-16 08:54:07,095 | INFO  | on(3)-10.0.0.122 | WorkServiceIT              
      | 89 - PAXEXAM-PROBE-dc3faa6e-521f-4883-b271-ec9928fb11b8 - 0.0.0 | 
Component 'org.alex.soto.ds.test.impl.FactoryComp' state 8
2017-02-16 08:54:07,098 | INFO  | : pid=my.config) | FactoryComp                
      | 11 - org.alex.soto.blueprint-ds-config-reload - 0.0.1.SNAPSHOT | 
Deactivated FactoryComp
2017-02-16 08:54:12,101 | INFO  | on(3)-10.0.0.122 | WorkServiceIT              
      | 89 - PAXEXAM-PROBE-dc3faa6e-521f-4883-b271-ec9928fb11b8 - 0.0.0 | 
System not healthy due to component 'org.alex.soto.ds.test.impl.FactoryComp' 
being not active. Current state: null.
{quote}

As of now, the component is deactivated upon a change in its configuration, but 
it is never activated again.  Booter is properly notified when the component is 
deactivated.

> Factory component fails to reactivate after config changes
> ----------------------------------------------------------
>
>                 Key: FELIX-5549
>                 URL: https://issues.apache.org/jira/browse/FELIX-5549
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>         Environment: Karaf 4.0.8
>            Reporter: Alex Soto
>
> A factory component fails to reactive after the configuration changes.  
> Initially, the component initializes normally.  After it is in Active state, 
> the configuration referenced by the component _configurationPid_  changes, 
> which causes the component to not activate again.
> A minimal application demonstrating this behavior is available here:
> https://github.com/lexsoto/blueprint-ds-config-reload



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

Reply via email to