Skip to main content


Eclipse Community Forums

      Home
Home » Eclipse Projects » Virgo » ActiveMQ Resolving error
ActiveMQ Resolving error [message #893088] Mon, 02 July 2012 10:52 Go to next message
Eclipse UserFriend
I am getting this exception, can anyone help me understand what is the resolving problem.

org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'app.amq' at version '2.2.1.7': Cannot resolve: app.amq
    Resolver report:
        An Import-Package could not be resolved. Caused by missing constraint in bundle <app.amq_2.2.1.7>
             constraint: <Import-Package: org.apache.activemq.xbean; version="[5.6.0,6.0.0)"> constrained to bundle <org.apache.activemq.activemq-core> constrained bundle version range "[5.6.0,5.6.0]"
        An Import-Package could not be resolved. Caused by missing constraint in bundle <org.fusesource.hawtdispatch.hawtdispatch-scala_1.9.0>
             constraint: <Import-Package: scala; version="0.0.0">
        An Import-Package could not be resolved. Caused by missing constraint in bundle <org.fusesource.hawtdispatch.hawtdispatch-scala_1.9.0>
             constraint: <Import-Package: scala.collection; version="0.0.0">
        An Import-Package could not be resolved. Caused by missing constraint in bundle <org.fusesource.hawtdispatch.hawtdispatch-scala_1.9.0>
             constraint: <Import-Package: scala.collection.generic; version="0.0.0">
        An Import-Package could not be resolved. Caused by missing constraint in bundle <org.fusesource.hawtdispatch.hawtdispatch-scala_1.9.0>
             constraint: <Import-Package: scala.collection.immutable; version="0.0.0">
        An Import-Package could not be resolved. Caused by missing constraint in bundle <org.fusesource.hawtdispatch.hawtdispatch-scala_1.9.0>
             constraint: <Import-Package: scala.collection.mutable; version="0.0.0">
        An Import-Package could not be resolved. Caused by missing constraint in bundle <org.fusesource.hawtdispatch.hawtdispatch-scala_1.9.0>
             constraint: <Import-Package: scala.reflect; version="0.0.0">
        An Import-Package could not be resolved. Caused by missing constraint in bundle <org.fusesource.hawtdispatch.hawtdispatch-scala_1.9.0>
             constraint: <Import-Package: scala.runtime; version="0.0.0">
        An Import-Package could not be resolved. Caused by missing constraint in bundle <org.fusesource.hawtdispatch.hawtdispatch-scala_1.9.0>
             constraint: <Import-Package: scala.util.continuations; version="0.0.0">
        An Import-Package could not be resolved. Caused by missing constraint in bundle <org.apache.commons.configuration_1.6.0>
             constraint: <Import-Package: org.apache.tools.ant.taskdefs; version="0.0.0">

        at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:45) ~[bundlefile:3.0.1.RELEASE]
        at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessTree(StandardPipeline.java:62) ~[bundlefile:3.0.1.RELEASE]
        at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessTree(CompensatingPipeline.java:72) ~[bundlefile:3.0.1.RELEASE]
        at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41) ~[bundlefile:3.0.1.RELEASE]
        at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessTree(StandardPipeline.java:62) ~[bundlefile:3.0.1.RELEASE]
        at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41) ~[bundlefile:3.0.1.RELEASE]
        at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:285) [bundlefile:3.0.1.RELEASE]
        at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:164) [bundlefile:3.0.1.RELEASE]
        at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:136) [bundlefile:3.0.1.RELEASE]
        at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:203) [bundlefile:3.0.1.RELEASE]
        at org.eclipse.virgo.kernel.userregion.internal.InitialArtifactDeployer$ArtifactDeployingRunnable.deployArtifacts(InitialArtifactDeployer.java:156) [org.eclipse.virgo.kernel.userregion-3.0.1.RELEASE.jar:3.0.1.RELEASE]
        at org.eclipse.virgo.kernel.userregion.internal.InitialArtifactDeployer$ArtifactDeployingRunnable.run(InitialArtifactDeployer.java:146) [org.eclipse.virgo.kernel.userregion-3.0.1.RELEASE.jar:3.0.1.RELEASE]
        at java.lang.Thread.run(Thread.java:636) [na:1.6.0_20]
Re: ActiveMQ Resolving error [message #893208 is a reply to message #893088] Tue, 03 July 2012 04:36 Go to previous messageGo to next message
Eclipse UserFriend
The problem is that this resolving issue happens randomly when deploying the apps plan, I guess the deployment order makes the difference, but I don't know how to find the actual cause.
Re: ActiveMQ Resolving error [message #893279 is a reply to message #893208] Tue, 03 July 2012 08:59 Go to previous message
Eclipse UserFriend
You can use the admin console in Virgo Tomcat Server or Virgo Jetty Server to browse the resolution failure state dump which will have been produced. It looks like there are some missing packages...
Previous Topic:Virgo Bundlor released
Next Topic:Virgo Tomcat Server for Apache Tomcat
Goto Forum:
  


Current Time: Wed Jul 23 01:51:26 EDT 2025

Powered by FUDForum. Page generated in 0.02847 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly