Skip to main content


Eclipse Community Forums

      Home
Home » Eclipse Projects » Virgo » Virgo upgrade from 3.6.3 on Java 7 to 3.6.4 on Java 8
Virgo upgrade from 3.6.3 on Java 7 to 3.6.4 on Java 8 [message #1738616] Thu, 21 July 2016 08:39 Go to next message
Eclipse UserFriend
We have Virgo 3.6.3 running on Java 7 and we would like to move to Java 8 so we tried to upgrade to Virgo 3.6.4 but we encountered a problem: our application doesn't start because of conflicts in uses conflict. Because of these conflicts one of our bundles cannot be loaded.

[2016-07-18 06:15:44.826] fs-watcher <HD0001I> Hot deployer processing 'INITIAL' event for file 'uc.plan'.
[2016-07-18 06:15:45.109] fs-watcher <DE0000I> Installing plan 'com.coradiant.console.plan' version '1.0.1.BUILD-SNAPSHOT'.
[2016-07-18 06:15:45.197] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.components-data' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:45.332] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.components-configuration' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:45.426] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.components-services' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:45.487] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-rest' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:45.542] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-validation' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:45.905] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-security' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:45.944] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-api-dashboard' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:46.063] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-dashboard' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:46.153] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-integration' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:46.297] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-node' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:46.316] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-api-i18n' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:46.336] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-i18n' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:46.387] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-layout' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:46.424] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-api-plugin' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:46.458] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-plugin' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:46.632] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-web-update' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:47.275] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-ui-components' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:47.407] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-root-webapp' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:15:48.985] fs-watcher <DE0000I> Installing bundle 'com.bmc.bsm.console-webapp' version '1.3.1.BMC-BUILD-SNAPSHOT'.
[2016-07-18 06:17:03.430] fs-watcher <DE0002E> Installation of plan 'com.coradiant.console.plan' version '1.0.1.BUILD-SNAPSHOT' failed. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: commit failed
at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.CommitStage.process(CommitStage.java:40)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessGraph(CompensatingPipeline.java:73)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:359)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:185)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:140)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:253)
at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225)
at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.deployIfNotDeployed(HotDeployerFileSystemListener.java:237)
at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:88)
at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:380)
at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:289)
at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:49)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.osgi.framework.BundleException: Failed to start bundle 'com.sun.jersey.contribs.jersey-spring' version '1.9.1'
at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.startBundle(StandardQuasiFramework.java:386)
at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.startBundles(StandardQuasiFramework.java:376)
at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.commit(StandardQuasiFramework.java:365)
at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.CommitStage.process(CommitStage.java:38)
... 16 common frames omitted
Caused by: org.osgi.framework.BundleException: The bundle "com.sun.jersey.contribs.jersey-spring_1.9.1 [173]" could not be resolved. Reason: Package uses conflict: Import-Package: org.springframework.aop.support; version="3.0.0", Package uses conflict: Import-Package: org.springframework.aop.framework; version="3.0.0", Package uses conflict: Import-Package: org.springframework.beans.factory.config; version="3.0.0", Package uses conflict: Import-Package: org.springframework.web.context.support; version="3.0.0", Package uses conflict: Import-Package: org.springframework.beans.factory; version="3.0.0", Package uses conflict: Import-Package: org.springframework.context; version="3.0.0", Package uses conflict: Import-Package: org.springframework.aop; version="3.0.0"
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:292)
at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.startBundle(StandardQuasiFramework.java:384)
... 19 common frames omitted

When we try Virgo 3.6.4 with Java 7 all our bundles do load successfully.
In addition we did all the tests above on Gentoo Linux (our production environment) but on Windows 7 (our dev environments) Virgo 3.6.4 + Java 8 does load all our bundles successfully.

Additional test that we did was to run our plan in two stages we first loaded a part 1 of the plan with all the bundles except the last one (we want to delay load the last bundle because the last bundle is the one that failed to load in the try above) and then we loaded part 2 of the plan with only the last bundle. This way the last bundle did load successfully.

Any assistance would greatly appreciated.
  • Attachment: virgo.log
    (Size: 1.68MB, Downloaded 250 times)
Re: Virgo upgrade from 3.6.3 on Java 7 to 3.6.4 on Java 8 [message #1738633 is a reply to message #1738616] Thu, 21 July 2016 10:36 Go to previous message
Eclipse UserFriend
Hi,

You cannot run Virgo 3.6 with Java8.

Virgo 3.6.4 can be run using Java6 or Java7 and will always "export" for the applications a Java6 API level.

Virgo 3.7 (currently available as milestone release) can be run using Java7 or Java8 and will always "export" for the applications a Java7 API level.

GianMaria.
Previous Topic:Virgo 3.6.4 + Apache CXF 3.1.4 = ClassNotFound
Next Topic:Active production installations?
Goto Forum:
  


Current Time: Mon Jun 16 04:07:57 EDT 2025

Powered by FUDForum. Page generated in 0.05594 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