[
https://issues.apache.org/jira/browse/FELIX-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-3554.
--------------------------------------
Resolution: Fixed
With the implementation of keeping and checking revision numbers of assigned
configurations, it can now be prevented to call the same service multiple times
with the same configuration version
> Prevent same configuration to be delivered multiple times
> ---------------------------------------------------------
>
> Key: FELIX-3554
> URL: https://issues.apache.org/jira/browse/FELIX-3554
> Project: Felix
> Issue Type: Task
> Components: Configuration Admin
> Affects Versions: configadmin-1.2.8
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: configadmin-1.6.0
>
>
> It may happen, that configuration is delivered to a ManagedService[Factory]
> twice depending some timing issues.
> Here's the thing:
> * Thread1: Configuration pid1 is created
> * Thread1: ManagedServiceUpdate is scheduled (but not run yet)
> * Thread1: ManagedService for pid1 is registered and configuration
> provisioning scheduled (but not run yet)
> * Thread2: Configuration update for pid1 is dispatched to ManagedService
> on separate thread
> * Thread2: ManagedService is updated with configured due to its
> registration
> The second configuration update is not completely wrong but is not needed and
> might be prevented if the configuration revision counter would be checked
> before providing the configuration to the ManagedService.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
