Hi Oleg, well, I've never installed from here ( I did not even looked before). Will try it for my self also. In Git repository I used 4.1.x and 4.2.x.
I guess 4.1.x is more "stable" for production. I've just started using 4.2. I was on 4.0.9 till previous week. I am doing upgrade across nodes. Kind Regards, Miroslav 2018-07-24 17:21 GMT+02:00 Oleg Cohen <[email protected]>: > Hi Miroslav, > > I got apache-karaf-4.2.0.tar.gz binary distribution from here > http://karaf.apache.org/download.html > > I can definitely try building from Git. Let me try … > > Thank you! > Oleg > > On Jul 24, 2018, at 11:17 AM, Miroslav Beranič < > [email protected]> wrote: > > Hi Oleg, > > where from did you deployed Karaf? You build it from the source or some > pre-compiled package/distribution? > > In general this is saying you are missing JAR ( but I guess you know > already this ). > > ( I've deployed multiple times - in past week - Karaf on RHEL 7.5 and I > had no such problem - but I was building from the GitHub git repository ) > > Kind Regards, > Miroslav > > > 2018-07-24 17:11 GMT+02:00 Oleg Cohen <[email protected]>: > >> Greetings, >> >> I have deployed Karaf v4.2.0 into a Linux RH 7.5 server. >> >> When I run Karaf as a service I get the following error in the log >> multiple times: >> >> >> 2018-07-24T11:07:12,176 | ERROR | features-3-thread-1 | Felix >> | - - | Bundle org.apache.felix.framework [0] >> EventDispatcher: Error during dispatch. (*java.lang.NoClassDefFoundError: >> org/apache/karaf/specs/locator/OsgiLocator*) >> java.lang.NoClassDefFoundError: org/apache/karaf/specs/locator >> /OsgiLocator >> at org.apache.karaf.specs.activator.Activator.register(Activator.java:124) >> ~[?:?] >> at >> org.apache.karaf.specs.activator.Activator.bundleChanged(Activator.java:96) >> ~[?:?] >> at org.apache.felix.framework.EventDispatcher.invokeBundleListe >> nerCallback(EventDispatcher.java:915) ~[?:?] >> at >> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:834) >> ~[?:?] >> at >> org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:516) >> ~[?:?] >> at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4579) >> ~[?:?] >> at >> org.apache.felix.framework.StatefulResolver.fireResolvedEvents(StatefulResolver.java:1289) >> ~[?:?] >> at >> org.apache.felix.framework.StatefulResolver.resolve(StatefulResolver.java:512) >> ~[?:?] >> at org.apache.felix.framework.Felix.resolveBundles(Felix.java:4108) >> ~[?:?] >> at org.apache.felix.framework.FrameworkWiringImpl.resolveBundle >> s(FrameworkWiringImpl.java:133) ~[?:?] >> at org.apache.karaf.features.internal.service.BundleInstallSupp >> ortImpl.resolveBundles(BundleInstallSupportImpl.java:240) ~[?:?] >> at org.apache.karaf.features.internal.service.FeaturesServiceIm >> pl.resolveBundles(FeaturesServiceImpl.java:1131) ~[?:?] >> at >> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:982) >> ~[?:?] >> at org.apache.karaf.features.internal.service.FeaturesServiceIm >> pl.doProvision(FeaturesServiceImpl.java:1025) ~[?:?] >> at org.apache.karaf.features.internal.service.FeaturesServiceIm >> pl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964) ~[?:?] >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) >> [?:?] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) >> [?:?] >> at java.lang.Thread.run(Thread.java:748) [?:?] >> >> I would appreciate help with fixing this problem of finding a workaround! >> >> Best, >> Oleg >> > > > > -- > Miroslav Beranič > MIBESIS > +386(0)40/814-843 > [email protected] > http://www.mibesis.si > > > -- Miroslav Beranič MIBESIS +386(0)40/814-843 [email protected] http://www.mibesis.si
