Page History

...

1. In the example above, if you are unable to osgi install -s mvn:http://people.apache.org/repo/m2-snapshot-repository!org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-impl-2.1.6/4.0-m2-SNAPSHOT, it is very likely because you do not have this JAR in your local repository and Pax URL is not configured to allow SNAPSHOT downloads from people.apache.org. To fix, edit etc/org.ops4j.pax.url.mvn.cfg and uncomment the last line to the following:

   Code Block
   org.ops4j.pax.url.mvn.repositories=+http://people.apache.org/repo/m2-snapshot-repository/<at:var at:name="snapshots" />noreleases

2. If you build from source, your startup output may have a long list of startup dependencies that were not found. While these are referenced from etc/startup.properties and located in system, the features build (via http://svn.apache.org/repos/asf/servicemix/smx4/features/trunk/ relies on artifacts included in the NMR and kernel builds. Check these out and install them, then do a 'clean install' on the features build.
3. Launching SMX4 can result in a deadlock in Felix during module dependency resolution. This is often a result of sending a SIGINT (control-C) to the process when it will not cleanly exit. This can corrupt the caches and cause startup problems in the very next launch. It is fixed by emptying the component cache:

   Code Block
   rm -rf data/cache/*

Summary

This document showed you how simple it is to have Apache ServiceMix Kernel up and running. The overall time for getting the server running should be less than five minutes if you have the prerequisite (Java 1.5) already installed. Additionally, this article also showed you how to deploy and test a simple Camel application in less than five minutes.

...