A refresh is *needed* when the administrator is finished installing, updating and uninstalling bundles. So there has to be some kind of "boundary" that marks the end of the set of operations. FileInstall does not and cannot have such a boundary, so it is forced to refresh continuously.
For this reason I don't recommend using FileInstall in production applications. It's fine for development and prototyping, but in a production system you need more control. Neil On Tue, Dec 18, 2012 at 9:08 PM, Raul Kripalani <[email protected]> wrote: > Hi all, > > Is it possible to avoid framework refreshes when File Install adds a > bundle? In some cases, refreshing the framework could be somewhat > destructive. > > Right now I'm facing a situation where values of MDC logging disappear in > log4j appenders (I know it sounds random, but it's true). My setup: Karaf > 2.2.9 with Equinox and Camel 2.10.3. > > I've been able to trace this situation to when Commons FileUpload is > dropped inside deploy/, which ends up refreshing Spring Web (has an > optional dependency to FileUpload). > > The refresh percolates up to the top due to transitive imports, probably > reaching the Pax Logging bundles. As a result, MDC stops working > altogether, likely related to the new classloader spaces and static > ThreadLocal fields. > > Thanks for your help! > > Regards, > > *Raúl Kripalani* > Apache Camel Committer > Enterprise Architect, Program Manager, Open Source Integration specialist > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani > http://blog.raulkr.net | twitter: @raulvk <http://twitter.com/raulvk> >
