karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Otasek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-5773) org.apache.karaf.specs.locator not in java.base with Java 10 in Windows
Date Fri, 15 Jun 2018 22:14:00 GMT

    [ https://issues.apache.org/jira/browse/KARAF-5773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514430#comment-16514430
] 

David Otasek commented on KARAF-5773:
-------------------------------------

I've tracked down this source of this error, and it appears to have come from some script
customization we did on our distribution; stock Karaf 4.2.1-SNAPSHOT appears to work correctly.

> org.apache.karaf.specs.locator not in java.base with Java 10 in Windows
> -----------------------------------------------------------------------
>
>                 Key: KARAF-5773
>                 URL: https://issues.apache.org/jira/browse/KARAF-5773
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 4.2.1
>         Environment: Microsoft Windows 10 Enterprise
> Version 10.0.15063 Build 15063
> java version "10" 2018-03-20
> Java(TM) SE Runtime Environment 18.3 (build 10+46)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10+46, mixed mode)
>            Reporter: David Otasek
>            Priority: Major
>
> When starting Karaf in Windows with Java 10, I get the following warning:
> {quote}WARNING: package org.apache.karaf.specs.locator not in java.base{quote}
> When I then attempt to start bundles from within Java, I get stack traces similar to
the following: 
> {quote}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.invokeBundleListenerCallback(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.resolveBundleRevision(Felix.java:4144)
>  at org.apache.felix.framework.Felix.startBundle(Felix.java:2119)
>  at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
>  at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
>  at org.cytoscape.rest.internal.task.OSGiJAXRSManager.installFeature(OSGiJAXRSManager.java:125)
>  at org.cytoscape.rest.internal.task.OSGiJAXRSManager.installOSGiJAXRSBundles(OSGiJAXRSManager.java:94)
>  at org.cytoscape.rest.internal.CyActivator.lambda$startCyREST$0(CyActivator.java:275)
>  at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>  at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
>  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>  at java.base/java.lang.Thread.run(Unknown Source)
> {quote}
> The same code works without the warning in Linux with Java 10. 
> Both configurations have the changes I outlined in (https://issues.apache.org/jira/browse/KARAF-5705) which
address another problem that was causing errors and limiting functionality.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message