A framework is bootstraped by a OSGiBootstrapProvider which provides functionality that is not available in the standard OSGi lauch API. For example it is standardized that a framework is launched using a property map, but not where these properties come from. Initial framework provisioning is also not standardized. With felix, equinox and jbmsc we use the PropertiesBootstrapProvider. More precisely, felix and equinox use a subclass of the PropertiesBootstrapProvider and jbmsc uses it directly (because it already contains the functionality jbmsc needs). The FelixBoostrapProvider, for example, sets a special Logger object.

Part of our bootstrap functionality is also the registration of initial services. What we see here is that Felix cannot register the DeployerService and the DeploymentRegistryService any more. The jbosgi-hotdeploy and jbosgi-webconsole use these services for bundle deployment.

Because we discontinued support for felix and equinox in the runtime and in AS, I removed the dependency on those services from the felix/equinox bootstrap providers. See: http://github.com/jbosgi/jbosgi-felix/commit/fcd2a9f52b45fac6bd25c1b68e609f911246cc72

It is likely, that you are not using the latest jbosgi-felix because it is not build as part of the reactor. I'll fix that.

On branch http://github.com/jbosgi/jbosgi/tree/jbosgi362 I fixed a ton of issues with the result that all example and functional tests now run on jbmsc. Doing so I added a fair amount of functionality to jbosgi-container. I'll merge this to trunk and change the installer to use jbmsc. When done I'll have a look at your BundleSmokeTestCase and see if I can get it running on the supported frameworks.

Could you please add meaningful javadoc to http://github.com/jbosgi/jbosgi/blob/master/testsuite/performance/src/test/java/org/jboss/osgi/test/performance/bundle/BundleSmokeTestCase.java and its associates?

Fixed the MSC test run: http://github.com/jbosgi/jbosgi/commit/5f31e23c87d1f3f2197fc34466ad805f1c8ea005

There are however a number of resolver issues

2010-07-21 06:46:37,784 DEBUG [org.jboss.osgi.resolver.felix.LoggerDelegate] Conflict between imports
org.apache.felix.framework.resolver.ResolveException: Constraint violation for package 'org.jboss.osgi.test.common' when resolving module Module[Bundle-Thread_1_-0:0.0.0] between existing import Module[CommonBundle1:0.0.0].org.jboss.osgi.test.common BLAMED ON [[Module[Bundle-Thread_1_-0:0.0.0]] package; (&(package=org.jboss.osgi.test.common)(version>=1.0.0)(version<=1.0.0))] and uses constraint Module[CommonBundle5:0.0.0].org.jboss.osgi.test.common BLAMED ON [[Module[Bundle-Thread_1_-0:0.0.0]] package; (&(package=org.jboss.osgi.test.versioned.impl)(version>=1.0.0)(version<=1.0.0)), [Module[VersionedImplBundle1:0.0.0]] package; (package=org.jboss.osgi.test.util1), [Module[Util1:0.0.0]] package; (package=org.jboss.osgi.test.common)]
    at org.apache.felix.framework.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:992)
    at org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:108)
    at org.jboss.osgi.resolver.felix.ResolverExt.resolve(ResolverExt.java:51)
    at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:152)
    at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:107)
    at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:181)
    at org.jboss.osgi.container.plugin.internal.ResolverPluginImpl.resolve(ResolverPluginImpl.java:92)
    at org.jboss.osgi.container.bundle.HostBundle.startInternal(HostBundle.java:315)
    at org.jboss.osgi.container.bundle.HostBundle.start(HostBundle.java:299)
    at org.jboss.osgi.container.bundle.AbstractBundle.start(AbstractBundle.java:429)
    at org.jboss.osgi.container.bundle.BundleWrapper.start(BundleWrapper.java:166)
    at org.jboss.osgi.test.performance.bundle.BundleInstallAndStartBenchmark.runThread(BundleInstallAndStartBenchmark.java:153)
    at org.jboss.osgi.test.performance.bundle.BundleSmokeTestCase.test5(BundleSmokeTestCase.java:94)

Not sure if this is meant to happen.

felix and jbossmc - ok

equinox cannot find the test class

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.157 sec <<< FAILURE!
test5(org.jboss.osgi.test.performance.bundle.BundleSmokeTestCase)  Time elapsed: 0.037 sec  <<< ERROR!
java.lang.ClassNotFoundException: org.jboss.osgi.test.performance.bundle.BundleSmokeTestCase
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:494)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:326)
    at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:231)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1193)
    at org.jboss.arquillian.osgi.ArquillianBundleActivator$1.loadTestClass(ArquillianBundleActivator.java:62)

I suggest we focus on jbmsc in comparison with felix

BTW, I think the arq guys must be joking with: arquillian-protocol-jmx-osgi-bundle.jar

Whats wrong with arquillian-bundle.jar ;-)

Can this be isolated in a dedicated core test case that is associated with a jira?

If it's a bug we need to see that it gets fixed in the felix resolver.