Hi!
I have investigated the issue more thoroughly and found out that all our
service units fail whose service-engines are servicemix-components. So
servicemix-http, servicemix-bean, servicemix-jms and servicemix-drools
service-units all fail with exceptions similar to the one I mentioned
below or sometimes with the exception directly below. We use for our
components the versions 2010.01 and have moved to the next Snapshot of
ServiceMix 4.1.0 (build 221).
Here is the stacktrace:
javax.jbi.JBIException: java.lang.reflect.InvocationTargetException
at
org.apache.servicemix.jbi.deployer.impl.ComponentInstaller.install(ComponentInstaller.java:159)
...
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.geronimo.blueprint.container.AbstractServiceReferenceRecipe$JdkProxyFactory$1.invoke(AbstractServiceReferenceRecipe.java:561)
at $Proxy30.manageObject(Unknown Source)
at
org.apache.servicemix.jbi.deployer.impl.Deployer.registerComponent(Deployer.java:441)
at
org.apache.servicemix.jbi.deployer.impl.ComponentInstaller.initComponent(ComponentInstaller.java:427)
at
org.apache.servicemix.jbi.deployer.impl.ComponentInstaller.install(ComponentInstaller.java:143)
... 33 more
Caused by: javax.management.JMException
at
org.apache.servicemix.nmr.management.ManagementAgent.manageNamedObject(ManagementAgent.java:103)
at
org.apache.servicemix.nmr.management.ManagementAgent.manageObject(ManagementAgent.java:78)
... 41 more
Caused by: javax.management.JMException
at
org.apache.servicemix.nmr.management.ManagementAgent.register(ManagementAgent.java:248)
at
org.apache.servicemix.nmr.management.ManagementAgent.register(ManagementAgent.java:231)
at
org.apache.servicemix.nmr.management.ManagementAgent.manageNamedObject(ManagementAgent.java:101)
... 42 more
I took a look at the cxf-wsdl-first examples and compared the service
unit there to our service-units, but could not find a difference.
Are there any special issues which occur when service-units for the
servicemix service-engines are migrated from 4.0.0 to 4.1.0?
Thank you in advance for your help!
Kind regards,
Michael Handler
Am 31.03.2010 12:39, schrieb Michael Handler:
Hi!
I'm trying to deploy our project on ServiceMix 4.1.0-Snapshot (from
today- build 220).
It fails with the following stack trace:
[INFO] servicemix-http is not deployed
[INFO] Deploying jbi-component from
C:\Users\Michi\.m2\repository\org\apache\servicemix\servicemix-http\2010.01\servicemix-http-2010.01-installer.zip
...
org.apache.servicemix.jbi.deployer.impl.PendingException:
SharedLibrary not installed: servicemix-shared
at
org.apache.servicemix.jbi.deployer.impl.ComponentInstaller.init(ComponentInstaller.java:113)
at
org.apache.servicemix.jbi.deployer.impl.InstallationService.doLoadNewInstaller(InstallationService.java:219)
at
org.apache.servicemix.jbi.deployer.impl.InstallationService.install(InstallationService.java:165)
at
org.apache.servicemix.jbi.deployer.impl.AdminCommandsImpl.installComponent(AdminCommandsImpl.java:56)
Could anyone help me to resolve this issue? How do I install shared
libraries?
features:list gives me the following output:
ka...@root> features:list | grep servicemix-shared
[installed ] [2010.01 ] servicemix-shared
repo-0
kind regards,
Michael
