Hello For the record, the race condition between FeatureConfigInstaller and Felix Fileinstall was fixed in https://issues.apache.org/jira/browse/KARAF-7389 for Karaf 4.3.8 and 4.4.1.
Can we see the logs for the issue? regards Grzegorz Grzybek pon., 9 gru 2024 o 21:26 James Ziesig <james.zie...@broadcom.com> napisał(a): > Hi Chandan, > > We were having very similar problems after we moved to Karaf 4. I was > able to readily reproduce the problem in the base karaf 4.4.3. I found > that if I modified startup.properties to start fileinstall at level 9 so > that it starts before configadmin, the problem ceased. > > We deploy with that change and haven't seen the problem since. > I hope that helps, > > Jim > > > On Mon, Dec 9, 2024 at 3:06 PM James Bushel <jimnz...@gmail.com> wrote: > >> Hi Chandan >> >> This sounds like an issue that’s been around for quite some time. Do you >> have multiple bundles sharing the same configuration file? If you do the >> trick is to create symlinks to the one config file, and give each of the >> bundles that symlink name, which then gives them each a virtual separate >> config file name. >> >> I haven’t tried newer karaf version to see if this is fixed as the >> workaround has never failed me. >> >> -- James >> >> >> > On 2024-12-10, at 06:07, Chandan Singh <mailbox.chandansi...@gmail.com> >> wrote: >> > >> > >> > Hi all , >> > >> > We are facing an issue where we notice some of the config files in the >> etc folder are getting blanked during karafs restart randomly . Has >> anyone faced anything that needs to be checked / configured ? We are >> facing this in karaf 4.3.10 .. These files are our custom config files/ >> where we have mvn setting etc . >> > >> > >> > Regards >> > Chandan >> > > This electronic communication and the information and any files > transmitted with it, or attached to it, are confidential and are intended > solely for the use of the individual or entity to whom it is addressed and > may contain information that is confidential, legally privileged, protected > by privacy laws, or otherwise restricted from disclosure to anyone else. If > you are not the intended recipient or the person responsible for delivering > the e-mail to the intended recipient, you are hereby notified that any use, > copying, distributing, dissemination, forwarding, printing, or copying of > this e-mail is strictly prohibited. If you received this e-mail in error, > please return the e-mail to the sender, delete it from your computer, and > destroy any printed copy of it.
