Reinstalling Feature Fails Caused By Cached Bundle ID
Hi all, We deploy Eclipse RAP application on Apache Karaf 3.0.8 w/ Equinox framework, so far so good on 1st deployment, but whenever I reinstall the dependency feature it fails with the following exception: 2017-06-30 12:49:57,282 | ERROR | nsole user karaf | ShellUtil | 43 - org.apache.karaf.shell.core - 4.0.8 | Exception caught while executing command org.apache.karaf.features.internal.util.MultiException: Error restarting bundles at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:868)[8:org.apache.karaf.features.core:4.0.8] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.8] at org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.8] at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66] at java.lang.Thread.run(Thread.java:745)[:1.8.0_66] Caused by: org.osgi.framework.BundleException: Exception in org.eclipse.equinox.http.registry.internal.Activator.start() of bundle org.eclipse.equinox.http.registry. at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:792)[org.eclipse.osgi-3.10.102.v20160118-1700.jar:] at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)[org.eclipse.osgi-3.10.102.v20160118-1700.jar:] at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:941)[org.eclipse.osgi-3.10.102.v20160118-1700.jar:] at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:318)[org.eclipse.osgi-3.10.102.v20160118-1700.jar:] at org.eclipse.osgi.container.Module.doStart(Module.java:571)[org.eclipse.osgi-3.10.102.v20160118-1700.jar:] at org.eclipse.osgi.container.Module.start(Module.java:439)[org.eclipse.osgi-3.10.102.v20160118-1700.jar:] at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:392)[org.eclipse.osgi-3.10.102.v20160118-1700.jar:] at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:411)[org.eclipse.osgi-3.10.102.v20160118-1700.jar:] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1287)[8:org.apache.karaf.features.core:4.0.8] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:860)[8:org.apache.karaf.features.core:4.0.8] ... 6 more Caused by: java.lang.NullPointerException: null values not allowed at org.eclipse.core.internal.registry.ReferenceMap.put(ReferenceMap.java:355) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.getBundle(RegistryStrategyOSGI.java:151) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:166) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) at org.eclipse.equinox.http.registry.internal.HttpContextManager.added(HttpContextManager.java:75) at org.eclipse.equinox.http.registry.internal.ExtensionPointTracker.open(ExtensionPointTracker.java:75) at org.eclipse.equinox.http.registry.internal.HttpContextManager.start(HttpContextManager.java:47) at org.eclipse.equinox.http.registry.internal.HttpRegistryManager.start(HttpRegistryManager.java:104) at org.eclipse.equinox.http.registry.internal.HttpServiceTracker.addingService(HttpServiceTracker.java:58) at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)[org.osgi.core-6.0.0.jar:] at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)[org.osgi.core-6.0.0.jar:] at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)[org.osgi.core-6.0.0.jar:] at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:183)[org.osgi.core-6.0.0.jar:] at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:318)[org.osgi.core-6.0.0.jar:] at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:261)[org.osgi.core-6.0.0.jar:] at org.eclipse.equinox.http.registry.internal.HttpServiceTracker.open(HttpServiceTracker.java:42) at org.eclipse.equinox.http.registry.internal.Activa
Re: Upgrading Karaf Equinox Framework Fails
Hi JB, Ah sure, why didn't I expect this folder. Thanks & Regards, SetNug -- View this message in context: http://karaf.922171.n3.nabble.com/Upgrading-Karaf-Equinox-Framework-Fails-tp4050595p4050597.html Sent from the Karaf - User mailing list archive at Nabble.com.
Upgrading Karaf Equinox Framework Fails
Hi all, I tried to upgrade Equinox that is used as Karaf framework by adding the following in custom.properties: karaf.framework.equinox=mvn\:org.eclipse.tycho/org.eclipse.osgi/3.10.102.v20160118-1700 But when I start Karaf (4.0.8) it complains for not being able to resolve it. I've checked & double checked that the path to Maven artefact is correct. Is there something I miss ? Thanks & Regards, SetNug -- View this message in context: http://karaf.922171.n3.nabble.com/Upgrading-Karaf-Equinox-Framework-Fails-tp4050595.html Sent from the Karaf - User mailing list archive at Nabble.com.
RE: Blueprint fails instantiating bean with generic constructor
Hi JP, Thanks. I've voted it. Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-fails-instantiating-bean-with-generic-constructor-tp4049986p4050004.html Sent from the Karaf - User mailing list archive at Nabble.com.
Blueprint fails instantiating bean with generic constructor
Hi all,
Aries Blueprint fails to instantiate bean with the following constructors:
public AggregateAnnotationCommandHandler(Class aggregateType,
Repository repository)
{
}
It seems to have problems with the second argument since it contains generic
parameter.
While it successfully instantiates the following bean:
public EventSourcingRepository(AggregateFactory aggregateFactory,
EventStore eventStore)
{
}
I'm using Apache Karaf 4.0.8.
Any insight would be greatly appreciated.
Thanks & Regards,
Setya
--
View this message in context:
http://karaf.922171.n3.nabble.com/Blueprint-fails-instantiating-bean-with-generic-constructor-tp4049986.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Blueprint and Custom Namespace
Hi Guillaume, Thanks. I've raised this JIRA <https://issues.apache.org/jira/browse/ARIES-1572> issue. Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-and-Custom-Namespace-tp4046737p4046849.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Blueprint and Custom Namespace
Hi Guillaume, This is how the classes are declared: public interface EventSqlSchema public class GenericEventSqlSchema implements EventSqlSchema public class OrientDbEventSqlSchema extends GenericEventSqlSchema And below is the configuration: Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-and-Custom-Namespace-tp4046737p4046847.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Blueprint and Custom Namespace
Hi Guillaume, I was referring to Blueprint parsing configuration problem if constructor parameter contains generics. Which is already solved according to this JIRA <https://issues.apache.org/jira/browse/ARIES-843> , with fixed version blueprint-core-1.0.1.jar, nevertheless I'm still experiencing it with Karaf 4.0.5 which contains blueprint-core-1.6.1.jar Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-and-Custom-Namespace-tp4046737p4046845.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Blueprint and Custom Namespace
Hi Guillaume, Sorry for this misunderstanding on my part. I assume Karaf 4.0.5 already contains the fix since it has blueprint-core-1.6.1 in it while in the JIRA the fix version is blueprint-core-1.0.1. Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-and-Custom-Namespace-tp4046737p4046831.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Blueprint and Custom Namespace
Hi Guillaume, Any update on this one ? The JIRA says it's been fixed but I'm still having problem in Karaf 4.0.5. Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-and-Custom-Namespace-tp4046737p4046825.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Blueprint and Custom Namespace
Hi, I've created this JIRA <https://issues.apache.org/jira/browse/ARIES-1567> issue. Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-and-Custom-Namespace-tp4046737p4046795.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Blueprint and Custom Namespace
ext@33268309 has not been refreshed yet at org.springframework.context.support.AbstractApplicationContext.assertBeanFactoryActive(AbstractApplicationContext.java:1041)[103:org.apache.servicemix.bundles.spring-context:4.2.5.RELEASE_1] at org.springframework.context.support.AbstractApplicationContext.getBeansOfType(AbstractApplicationContext.java:1161)[103:org.apache.servicemix.bundles.spring-context:4.2.5.RELEASE_1] at org.axonframework.contextsupport.spring.ApplicationContextLookupParameterResolverFactory.afterPropertiesSet(ApplicationContextLookupParameterResolverFactory.java:76)[115:org.axonframework.axon-core:2.4.3] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)[102:org.apache.servicemix.bundles.spring-beans:4.2.5.RELEASE_1] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)[102:org.apache.servicemix.bundles.spring-beans:4.2.5.RELEASE_1] ... 52 more/ While my Blueprint config is as simple as: /http://www.osgi.org/xmlns/blueprint/v1.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:axon="http://www.axonframework.org/schema/core"; xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd http://www.axonframework.org/schema/core http://www.axonframework.org/schema/axon-core.xsd";> / Any help would greatly appreciated. Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-and-Custom-Namespace-tp4046737p4046791.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Blueprint and Custom Namespace
Hi Guillaume, Thank you very much for your useful Maven bundle. This seems to be the only option to use Spring custom namespace in Blueprint. Currently I'm using Apache Karaf 4.0.5, but it seems to have problem wiring constructor containing parameters with generic. I detailed my explanation in this JIRA <https://issues.apache.org/jira/browse/ARIES-843> . Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-and-Custom-Namespace-tp4046737p4046775.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Blueprint and Custom Namespace
Hi, Thank you for your clarification. I've found bundle org.apache.aries.blueprint.spring, is this bundle supposed to enable Blueprint to recognize Spring's custom namespace ? Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-and-Custom-Namespace-tp4046737p4046739.html Sent from the Karaf - User mailing list archive at Nabble.com.
Blueprint and Custom Namespace
Hi all, In my Spring based application, I use custom namespaces from certain framework, for example: http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:axon="http://www.axonframework.org/schema/core"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://www.axonframework.org/schema/core http://www.axonframework.org/schema/axon-core.xsd";> If I migrate to Blueprint would I be able to use the same custom namespace as is ? Any insight would be greatly appreciated. Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-and-Custom-Namespace-tp4046737.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: All version of feature specified as dependent feature gets installed
Hi all, Turns out I have to specify the version in range as workaround: spring-jdbc Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/All-version-of-feature-specified-as-dependent-feature-gets-installed-tp4045991p4045992.html Sent from the Karaf - User mailing list archive at Nabble.com.
All version of feature specified as dependent feature gets installed
Hi all, In Apache Karaf 4.0.3 we have the following spring-jdbc features available: spring-jdbc|3.1.4.RELEASE spring-jdbc|3.2.14.RELEASE_1 spring-jdbc|4.0.7.RELEASE_3 spring-jdbc|4.1.7.RELEASE_2 spring-jdbc|4.2.2.RELEASE_1 When I install for specific version using the following command: karaf@root()> feature:install spring-jdbc/3.2.14.RELEASE_1 The version of spring-jdbc installed correctly. But when I put the feature as dependent feature for example: spring-jdbc and invoke command: karaf@root()> feature:install myfeature All versions except 3.1.4.RELEASE will be installed causing dependency conflict. This is against the documentation where only the specified version will be installed. Any insight would be greatly appreciated. Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/All-version-of-feature-specified-as-dependent-feature-gets-installed-tp4045991.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Deploying Exploded Folder to Apache Karaf
Hi All, Thank you all for your information. Will try it soon. Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Deploying-Exploded-Folder-to-Apache-Karaf-tp4045035p4045044.html Sent from the Karaf - User mailing list archive at Nabble.com.
Deploying Exploded Folder to Apache Karaf
Hi All, Does Karaf support exploded folder as deployment artifact ? I'm asking this because during testing I want to deploy/install entire Eclipse project without having to jar it first. Any information would be greatly appreciated. Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Deploying-Exploded-Folder-to-Apache-Karaf-tp4045035.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Bundle fails to start in Karaf 4.0.3 caused by Require-Capability
Hi Achim, I've added as per your suggestion, but it's still not working. Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Bundle-fails-to-start-in-Karaf-4-0-3-caused-by-Require-Capability-tp4044711p4044717.html Sent from the Karaf - User mailing list archive at Nabble.com.
Bundle fails to start in Karaf 4.0.3 caused by Require-Capability
Hi all, I'm using Karaf 4.0.3, when deploying org.apache.commons.lang <http://karaf.922171.n3.nabble.com/file/n4044711/org.jar> bundle it fails to start with the following exception: /Caused by: org.osgi.framework.BundleException: Could not resolve module: org.apache.commons.lang [246] Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JRE)(version=1.1))" at org.eclipse.osgi.container.Module.start(Module.java:434)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:393)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:412)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:] at org.apache.karaf.bundle.command.Install.execute(Install.java:96)[24:org.apache.karaf.bundle.core:4.0.3] ... 11 more/ It seems to be caused by given bundle containing the following entry in its MANIFEST.MF: /Bundle-RequiredExecutionEnvironment: JRE-1.1/ I've tried to add JRE-1.1 in etc/config.properties#org.osgi.framework.executionenvironment to no avail. Any help would be appreciated. Thanks & Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Bundle-fails-to-start-in-Karaf-4-0-3-caused-by-Require-Capability-tp4044711.html Sent from the Karaf - User mailing list archive at Nabble.com.
