Hello Short description - when using custom org.apache.felix.cm.PersistenceManager and felix.cm.pm context property, there's quite high chance of duplicate instances and registrations of ConfigurationAdmin activated by such PM. I found this problem when restarting a bundle that registers/unregisters custom PM.
Here's the issue: https://issues.apache.org/jira/browse/FELIX-6066 And here's the PR: https://github.com/apache/felix/pull/185 best regards Grzegorz Grzybek czw., 21 lut 2019 o 16:51 Grzegorz Grzybek <[email protected]> napisał(a): > Hello > > One moment - by coincidence, I've found some nasty race condition. Give me > few minutes to describe the problem in FELIX jira. > > Changing my vote to -1 (non-binding) for now. > > regards > Grzegorz Grzybek > > czw., 21 lut 2019 o 11:57 Timothy Ward <[email protected]> > napisał(a): > >> +1 >> >> Tim >> >> > On 21 Feb 2019, at 07:39, Georg Henzler <[email protected]> wrote: >> > >> > +1 (non-binding) >> > >> > -Georg >> > >> > On 2019-02-21 06:25, Francois Papon wrote: >> >> +1 (non-binding) >> >> Thanks! >> >> regards, >> >> François Papon >> >> [email protected] >> >> Le 20/02/2019 à 14:54, Carsten Ziegeler a écrit : >> >>> We solved two issues in this release: >> >>> >> http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.configadmin-1.9.12/changelog.txt >> >>> Staging repositories: >> >>> >> https://repository.apache.org/content/repositories/orgapachefelix-1287/ >> >>> You can use this UNIX script to download the release and verify the >> >>> signatures: >> >>> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh >> >>> Usage: >> >>> sh check_staged_release.sh 1287 /tmp/felix-staging >> >>> Please vote to approve this release: >> >>> [ ] +1 Approve the release >> >>> [ ] -1 Veto the release (please provide specific comments) >> >>> Regards >> >>> Carsten >> >>> -- >> >>> Carsten Ziegeler >> >>> Adobe Research Switzerland >> >>> [email protected] >> >>
