Major Description
Currently there are some init issues when running in an OSGi env - there can be more than one call to Oak#createContentRepository using the same NodeStore.
The overlap can come from having a Sling repo call #createContentRepository via the JCR class and at the same time have org.apache.jackrabbit.mk.osgi.MicroKernelService call #createContentRepository on the same NodeStore from the Activator.
The simplest solution for now is to have the oak-core Activator class ignore the NodeStore services and leave repo impls like the sling one call #createContentRepository.