camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raúl Kripalani (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (CAMEL-9082) Upgrade ServiceMix Specs to 2.5.0
Date Fri, 14 Aug 2015 18:38:47 GMT

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

Raúl Kripalani edited comment on CAMEL-9082 at 8/14/15 6:38 PM:
----------------------------------------------------------------

After the upgrade, on Karaf 2.4.3, all OK except camel-hazelcast (see below, it also failed
with specs 2.4.0 when other bundles dragged in their deps):

{code}
karaf@root> features:install camel-aws
karaf@root> features:install camel-groovy
karaf@root> features:install camel-hazelcast
Error executing command: Can't install feature camel-hazelcast/0.0.0:
Could not start bundle mvn:com.hazelcast/hazelcast/3.5.1 in feature(s) camel-hazelcast-2.16-SNAPSHOT,
camel-vertx-2.16-SNAPSHOT: Activator start error in bundle com.hazelcast [79].
karaf@root> features:install camel-hbase
karaf@root> features:install camel-script-jruby
karaf@root> features:install camel-script-javascript
karaf@root> features:install camel-script-groovy
karaf@root> features:install camel-script
karaf@root> features:install camel-sip
karaf@root> features:install camel-soap
karaf@root> features:install camel-core
karaf@root> features:install xml-specs-api
{code}

Where camel-hazelcast throws this exception:

{code}
aused by: org.osgi.framework.BundleException: Activator start error in bundle com.hazelcast
[188].
	at org.apache.felix.framework.Felix.activateBundle(Felix.java:2204)
	at org.apache.felix.framework.Felix.startBundle(Felix.java:2072)
	at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:976)
	at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:963)
	at org.apache.karaf.shell.osgi.InstallBundle.doExecute(InstallBundle.java:51)
	... 17 more
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_79]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_79]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_79]
	at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_79]
	at com.hazelcast.internal.osgi.Activator.activateJavaxScripting(Activator.java:70)
	at com.hazelcast.internal.osgi.Activator.start(Activator.java:46)
	at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
	at org.apache.felix.framework.Felix.activateBundle(Felix.java:2154)
	... 21 more
Caused by: java.lang.NoSuchMethodError: javax.script.ScriptEngineManager.setBindings(Ljavax/script/Bindings;)V
	at com.hazelcast.internal.osgi.OSGiScriptEngineManager.createScriptEngineManager(OSGiScriptEngineManager.java:262)
	at com.hazelcast.internal.osgi.OSGiScriptEngineManager.findManagers(OSGiScriptEngineManager.java:235)
	at com.hazelcast.internal.osgi.OSGiScriptEngineManager.<init>(OSGiScriptEngineManager.java:87)
	at com.hazelcast.internal.osgi.ScriptEngineActivator.registerOsgiScriptEngineManager(ScriptEngineActivator.java:44)
	... 29 more
{code}

This issue only occurs when certain other bundles are installed, either one of camel-aws or
camel-groovy are dragging some dependencies related to scripting (likely camel-groovy) that
the Hazelcast library doesn't like. Probably because they don't specify a version range in
their javax.script import:

{code}
[...]
Bundle-Vendor = Hazelcast, Inc.
Bundle-Activator = com.hazelcast.internal.osgi.Activator
Bundle-Name = hazelcast
Bundle-DocURL = http://www.hazelcast.com/
Bundle-Description = Core Hazelcast Module
Bundle-SymbolicName = com.hazelcast
Bundle-Version = 3.5.1
Bundle-License = http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-ManifestVersion = 2
[...]
Import-Package =
[...]
	javax.script,
[...]
{code}

We'll have to investigate further and perhaps open a ticket at Hazelcast.

I'll open a ticket to investigate first on our side.

But since this issue was also present with specs 2.4.0, the problem is not caused by upgrading
to specs 2.5.0.


was (Author: raulvk):
After the upgrade, on Karaf 2.4.3, all OK except camel-hazelcast (see below, it also failed
with specs 2.4.0 when other bundles dragged in their deps):

{code}
karaf@root> features:install camel-aws
karaf@root> features:install camel-groovy
karaf@root> features:install camel-hazelcast
Error executing command: Can't install feature camel-hazelcast/0.0.0:
Could not start bundle mvn:com.hazelcast/hazelcast/3.5.1 in feature(s) camel-hazelcast-2.16-SNAPSHOT,
camel-vertx-2.16-SNAPSHOT: Activator start error in bundle com.hazelcast [79].
karaf@root> features:install camel-hbase
karaf@root> features:install camel-script-jruby
karaf@root> features:install camel-script-javascript
karaf@root> features:install camel-script-groovy
karaf@root> features:install camel-script
karaf@root> features:install camel-sip
karaf@root> features:install camel-soap
karaf@root> features:install camel-core
karaf@root> features:install xml-specs-api
{code}

Where camel-hazelcast throws this exception:

{code}
aused by: org.osgi.framework.BundleException: Activator start error in bundle com.hazelcast
[188].
	at org.apache.felix.framework.Felix.activateBundle(Felix.java:2204)
	at org.apache.felix.framework.Felix.startBundle(Felix.java:2072)
	at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:976)
	at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:963)
	at org.apache.karaf.shell.osgi.InstallBundle.doExecute(InstallBundle.java:51)
	... 17 more
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_79]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_79]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_79]
	at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_79]
	at com.hazelcast.internal.osgi.Activator.activateJavaxScripting(Activator.java:70)
	at com.hazelcast.internal.osgi.Activator.start(Activator.java:46)
	at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
	at org.apache.felix.framework.Felix.activateBundle(Felix.java:2154)
	... 21 more
Caused by: java.lang.NoSuchMethodError: javax.script.ScriptEngineManager.setBindings(Ljavax/script/Bindings;)V
	at com.hazelcast.internal.osgi.OSGiScriptEngineManager.createScriptEngineManager(OSGiScriptEngineManager.java:262)
	at com.hazelcast.internal.osgi.OSGiScriptEngineManager.findManagers(OSGiScriptEngineManager.java:235)
	at com.hazelcast.internal.osgi.OSGiScriptEngineManager.<init>(OSGiScriptEngineManager.java:87)
	at com.hazelcast.internal.osgi.ScriptEngineActivator.registerOsgiScriptEngineManager(ScriptEngineActivator.java:44)
	... 29 more
{code}

This issue only occurs when certain other bundles are installed, either one of camel-aws or
camel-groovy are dragging some dependencies related to scripting (likely camel-groovy) that
the Hazelcast library doesn't like. Probably because they don't specify a version range in
their javax.script import:

{code}
[...]
Bundle-Vendor = Hazelcast, Inc.
Bundle-Activator = com.hazelcast.internal.osgi.Activator
Bundle-Name = hazelcast
Bundle-DocURL = http://www.hazelcast.com/
Bundle-Description = Core Hazelcast Module
Bundle-SymbolicName = com.hazelcast
Bundle-Version = 3.5.1
Bundle-License = http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-ManifestVersion = 2
[...]
Import-Package =
[...]
	javax.script,
[...]
{code}

We'll have to investigate further and perhaps open a ticket at Hazelcast.

I'll open a ticket to investigate first on our side.

> Upgrade ServiceMix Specs to 2.5.0
> ---------------------------------
>
>                 Key: CAMEL-9082
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9082
>             Project: Camel
>          Issue Type: Task
>            Reporter: Raúl Kripalani
>            Assignee: Raúl Kripalani
>            Priority: Minor
>             Fix For: 2.16.0
>
>
> SMX team released a new version of the specs a few months ago. We should upgrade to it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message