Hello Guillaume, hello Andreas! Our problem is not the harmless exception "org.osgi.framework. BundleException: A fragment bundle cannot be started: com.awl.wlsi.extensions.pci-logging-extension_1.1.0.SNAPSHOT [3]" The problem is, that the bundle org.ops4j.pax.logging.pax-logging-service is not started anymore and we cannot start it by hand. This results that ServiceMix doesn't log anything into servicemix.log file. If we use org.ops4j.pax.logging.pax-logging-api as host bundle, we get an ClassNotFoundException, that the class com. awl.wlsi.extensions.pcilogging.PCIPatternLayout cannot be found.
Cheers, Christian On Mon, Dec 13, 2010 at 11:32 AM, Guillaume Nodet <gno...@gmail.com> wrote: > That's a bug in fileinstall which has been fixed, but it's quite harmless. > The reason is that OSGi fragments can not be started, only resolved, > but fileinstall did not check those. > You can safely ignore this error for now. > > On Mon, Dec 13, 2010 at 11:18, Christian Müller > <christian.muel...@gmail.com> wrote: > > Hello Niclas, hello Achim! > > > > Thank your for your answers. > > We trieyed Achim's proposed solution. We created a fragment bundle (see > > attachment for the OSGI bundle) which has this OSGI meta data in > > MANIFEST.MF: > > > > Fragment-Host: > > org.ops4j.pax.logging.pax-logging-service;bundle-version="[1.5.0,1.6.0)" > > > > > > We also changed the ServiceMix configuration file > > SERVICEMIX/etc/org.ops4j.pax.logging.cfg and instruct ServiceMix to use > our > > custom Layout class: > > > > > log4j.appender.out.layout=com.awl.wlsi.extensions.pcilogging.PCIPatternLayout > > > > > > We added this bundle to the SERVICEMIX/etc/startup.properties file direct > > after the pax logging bundles: > > > > org/ops4j/pax/logging/pax-logging-api/1.5.0/pax-logging-api-1.5.0.jar=8 > > > org/ops4j/pax/logging/pax-logging-service/1.5.0/pax-logging-service-1.5.0.jar=8 > > > com/awl/wlsi/extensions/pci-logging-extension/1.1.0-SNAPSHOT/pci-logging-extension-1.1.0-SNAPSHOT.jar=8 > > > > > > When we start ServiceMix, we can see the following message: > > > > Auto-properties start: org.osgi.framework.BundleException: A fragment > bundle > > cannot be started: > > com.awl.wlsi.extensions.pci-logging-extension_1.1.0.SNAPSHOT [3] > > > > > > Peculiarly the OSGI bundles are not started anymore: > > > > ka...@root> osgi:list > > START LEVEL 100 > > ID State Blueprint Spring Level Name > > [ 0] [Active ] [ ] [ ] [ 0] OSGi System Bundle > > (3.5.1.R35x_v20090827) > > [ 1] [Active ] [ ] [ ] [ 5] OPS4J Pax Url - > mvn: > > (1.1.2) > > [ 2] [Active ] [ ] [ ] [ 5] OPS4J Pax Url - > wrap: > > (1.1.2) > > [ 3] [Resolved ] [ ] [ ] [ 8] WLSI :: extensions > :: > > pci-logging-extension (1.1.0.SNAPSHOT) > > Hosts: 4 > > [ 4] [Resolved ] [ ] [ ] [ 8] OPS4J Pax Logging - > > Service (1.5.0) > > Fragments: 3 > > ... > > > > > > If we start the bundles, we get the following exceptions: > > > > ka...@root> start 4 > > You are about to access system bundle 4. Do you want to continue > (yes/no): > > Exception in org.ops4j.pax.logging.service.internal.Activator.start() of > > bundle org.ops4j.pax.logging.pax-logging-service. > > > > ka...@root> start 3 > > You are about to access system bundle 3. Do you want to continue > (yes/no): > > A fragment bundle cannot be started: > > com.awl.wlsi.extensions.pci-logging-extension_1.1.0.SNAPSHOT [3] > > > > > > Unfortunatly the servicemix log file is empty. > > > > Any ideas what we are doing wrong? > > > > Thanks in advance, > > Christian > > > > > > _______________________________________________ > > general mailing list > > general@lists.ops4j.org > > http://lists.ops4j.org/mailman/listinfo/general > > > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com >
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
