I think the main problem seems to be, the xml file was altered while karaf wasn't able to realize it's been altered. After the startup it still used the old one as there has already been a bundle generated for it. My best guess right now, this is due to the fact that karaf/FileInstaller wasn't "seeing" the change it wasn't able to "re-load" the change, make sure you alter it while Karaf is running then it will be able to get it faster.
regards, Achim 2014-08-11 9:22 GMT+02:00 Jean-Baptiste Onofré <[email protected]>: > It depends of the blueprint: if the parameters are directly in the > blueprint (not in cm), ConfigAdmin is not used at all. > > Regards > JB > > > On 08/11/2014 09:20 AM, Bram Pouwelse wrote: > >> I think the issue is that config admin stores the configuration >> internally (that would be where karaf caches the connection parameters) >> and that the datasource is created before the xml file is processed again. >> >> Regards, >> Bram >> >> >> 2014-08-11 9:09 GMT+02:00 Jean-Baptiste Onofré <[email protected] >> <mailto:[email protected]>>: >> >> >> Can you cleanup the data folder ? >> >> Regards >> JB >> >> >> On 08/11/2014 07:27 AM, [email protected] >> <mailto:[email protected]> wrote: >> >> I have an application that uses a postgresql database. I am using >> PGSimpleDataSource configured using a data source xml placed in >> $KARAF_HOME/deploy directory. Noticed an issue when the database >> xml >> file is modified. >> >> When I shutdown karaf, modify the data source XML to point to a >> different database and start karaf, it is still taking the old >> database >> connection parameters. If I restart again it connecting to the >> database >> that is configured in XML file. Is Karaf caching connection >> parameters ? >> >> regards >> >> Vinu >> >> The information contained in this electronic message and any >> attachments >> to this message are intended for the exclusive use of the >> addressee(s) >> and may contain proprietary, confidential or privileged >> information. If >> you are not the intended recipient, you should not disseminate, >> distribute or copy this e-mail. Please notify the sender >> immediately and >> destroy all copies of this message and any attachments. >> >> WARNING: Computer viruses can be transmitted via email. The >> recipient >> should check this email and any attachments for the presence of >> viruses. >> The company accepts no liability for any damage caused by any >> virus >> transmitted by this email. >> >> www.wipro.com <http://www.wipro.com> >> >> >> -- >> Jean-Baptiste Onofré >> [email protected] <mailto:[email protected]> >> >> http://blog.nanthrax.net >> Talend - http://www.talend.com >> >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Software Architect / Project Manager / Scrum Master
