Andreas, I finally got some time today to figure out a simple way to recreate it, and it is simple.
1. Start with the lastest SMX trunk 2. Build apache-servicemix-minimal assembly. 3. Deploy and run to verify it starts normally without any oddness 4. Modify the src/main/filtered-resources/etc/org.apache.karaf.features.cfg file and change the featuresBoot to the following: featuresBoot=karaf-framework,config,transaction,eventadmin,management,activemq-blueprint,activemq-web-console,webconsole,cxf,camel,camel-blueprint,camel-activemq 5. Rebuild the assembly 6. Deploy and run On that last run I will see double branding and errors about not being able to persist features. I am running on Mac OS X Lion and using the tar.gz deployment file if it matters. I've done this lots of different ways with both SMX 4.4.1 and SMX 4.5.0 starting points. I haven't started with just Karaf since I need all the features SMX integrates. After writing and testing all of that I just realized you can reproduce the problem by simply downloading the normal servicemix-minimal distro from the website and changing the featuresBoot as described above. No compiling required. Chris On Thu, Apr 19, 2012 at 12:20 AM, Andreas Pieber <[email protected]> wrote: > I know thos problems and they've encountered to me as I manipulated > the features.cfg in a way that the framework was started twice. Can > you write down an exact todo list to reproduce this issue? > > thx and kind regards, > Andreas > > On Wed, Apr 18, 2012 at 17:48, Chris Geer <[email protected]> wrote: > > As I've been getting more comfortable with Karaf (ServiceMix) I thought I > > was ready to be a little more adventurous and go ahead and build my own > > custom assembly with some upgraded packages I needed but I'm getting some > > odd behavior and I can't pinpoint what exactly caused the issue. Since > I'm > > essentially using ServiceMix I started with their assemblies as an > example > > to build mine and really only changed the package versions. > > - Camel 2.9.2-SNAPSHOT > > - CXF 2.5.2 > > > > When I start my distro though I get two odd things > > 1) The initial branding (logo and such) shows up twice > > 2) I get the following exception which shows up on the console, not log > > > > > > > org.apache.karaf.features.core[org.apache.karaf.features.internal.FeaturesServiceImpl] > > : Error persisting FeaturesService state > > java.lang.IllegalStateException: Invalid BundleContext. > > at > > > org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:365) > > at > > > org.apache.felix.framework.BundleContextImpl.getDataFile(BundleContextImpl.java:347) > > at > > > org.apache.karaf.features.internal.FeaturesServiceImpl.saveState(FeaturesServiceImpl.java:1049) > > at > > > org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:407) > > at > > > org.apache.karaf.features.internal.FeaturesServiceImpl$1.run(FeaturesServiceImpl.java:975) > > > > > org.apache.karaf.features.core[org.apache.karaf.features.internal.FeaturesServiceImpl] > > : Error persisting FeaturesService state > > java.lang.IllegalStateException: Invalid BundleContext. > > at > > > org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:365) > > at > > > org.apache.felix.framework.BundleContextImpl.getDataFile(BundleContextImpl.java:347) > > at > > > org.apache.karaf.features.internal.FeaturesServiceImpl.saveState(FeaturesServiceImpl.java:1049) > > at > > > org.apache.karaf.features.internal.FeaturesServiceImpl$1.run(FeaturesServiceImpl.java:980) > > > > Everything seems to run just fine but those seemed odd. What makes it > even > > weirder is that neither of those things happen on future launches of the > > container. Any thoughts on what might cause these and should I be > concerned? > > > > Thanks, > > Chris >
