You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/02/10 18:44:42 UTC
[jira] [Updated] (FELIX-5536) ConfigSpiOSGi may end with incomplete
realm due to race conditions
[ https://issues.apache.org/jira/browse/FELIX-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra updated FELIX-5536:
-----------------------------------
Summary: ConfigSpiOSGi may end with incomplete realm due to race conditions (was: ConfigSpiOSGi may end with in complete realm due to race conditions)
> ConfigSpiOSGi may end with incomplete realm due to race conditions
> ------------------------------------------------------------------
>
> Key: FELIX-5536
> URL: https://issues.apache.org/jira/browse/FELIX-5536
> Project: Felix
> Issue Type: Bug
> Components: JAAS
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: jaas-1.0.2
>
>
> Some race conditions around this have been fixed with FELIX-5505. However one more case surfaced where {{ConfigSpiOsgi#recreateConfigs}} can be invoked concurrently without lock from
> # {{ConfigSpiOsgi#updated}} - When ConfigurationAdmin dispatches config update for {{org.apache.felix.jaas.ConfigurationSpi}}
> # {{ConfigSpiOsgi#addingService}} - When some LoginModuleFactory is registered
> In such a case the setup may end up with incomplete realm where some LoginModuleFactory are missed out
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)