Community
Participate
Working Groups
Created attachment 268865 [details] 3.7.0.RELEASE log.log Using the JMX API to undeploy a previously deployed and active bundle fails. [2017-06-11 22:17:17.265] INFO start-signalling-1 org.eclipse.virgo.medic.eventlog.default WE0001I Started web bundle 'org.eclipse.virgo.samples.recipe.restservice' version '0.0.1.SNAPSHOT' with context path '/restservice-guide'. [2017-06-11 22:17:17.266] INFO start-signalling-1 org.eclipse.virgo.medic.eventlog.default DE0005I Started bundle 'org.eclipse.virgo.samples.recipe.restservice' version '0.0.1.SNAPSHOT'. [2017-06-11 22:17:17.266] INFO start-signalling-1 o.e.v.k.i.artifact.internal.bundle.BundleThreadContextManager Thread context class loader 'KernelBundleClassLoader: [bundle=org.eclipse.virgo.samples.recipe.restservice_0.0.1.SNAPSHOT]' popped and set to 'org.eclipse.core.runtime.internal.adaptor.ContextFinder@b345e4a' [2017-06-11 22:23:28.636] ERROR TCP Connection(5)-127.0.0.1 org.eclipse.virgo.medic.eventlog.default DE0506E Cannot undeploy bundle 'org.eclipse.org.eclipse.virgo.samples.recipe.restservice' version '0.0.1.SNAPSHOT'. Artifact not found. Attached is the full log of the server being started, the WAB being deplyed and then the attempt at undeploying the WAB.
Hi Bill I've used the jconsole and I was able to undeploy active bundles. Reproducing the behavior you describe was not possible for me. Can you please give more information on how I can reproduce? Regards, Dani
Created attachment 268953 [details] maven pom for org.eclipse.virgo.samples.recipe.restservice Here is the POM I am using to deploy and undeploy the WAB. Using "mvn virgo:deploy" and "mvn virgo:undeploy" results int the observed behaviour.