We're updating the issue view to help you get more done. 

Jetty container shows exception logs when the ROOT context is undeployed with Codehaus Cargo

Description

After running the undeploy command with the cargo-maven2-plugin against a remote Jetty 9.x container, Jetty outputs the following:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 830742 [qtp60830820-18] INFO o.e.j.server.handler.ContextHandler - Stopped o.e.j.w.WebAppContext@7e557003{ROOT,/,null,UNAVAILABLE}{C:\work\hosting\server\lucee-base\webapps\ROOT.war} 832689 [Scanner-0] WARN o.e.jetty.deploy.DeploymentManager - Unable to reach node goal: undeployed java.lang.IllegalArgumentException: Unknown bean o.e.j.w.WebAppContext@7e557003{ROOT,/,null,UNAVAILABLE}{C:\work\hosting\server\lucee-base\webapps\ROOT.war} at org.eclipse.jetty.util.component.ContainerLifeCycle.unmanage(ContainerLifeCycle.java:490) at org.eclipse.jetty.deploy.bindings.StandardStopper.processBinding(StandardStopper.java:41) at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:192) at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:505) at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:465) at org.eclipse.jetty.deploy.DeploymentManager.removeApp(DeploymentManager.java:416) at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileRemoved(ScanningAppProvider.java:209) at org.eclipse.jetty.deploy.providers.WebAppProvider.fileRemoved(WebAppProvider.java:473) at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileRemoved(ScanningAppProvider.java:76) at org.eclipse.jetty.util.Scanner.reportRemoval(Scanner.java:637) at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:535) at org.eclipse.jetty.util.Scanner.scan(Scanner.java:392) at org.eclipse.jetty.util.Scanner$1.run(Scanner.java:329) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source)

Status

Assignee

Unassigned

Reporter

Oblio Leitch

Components

Fix versions

Priority

Major