The problem is caused by the DeploymentControllerContext not getting removed, it is in the state of **ERROR**, but still available for the checkComplete() processing. | 2007-10-25 15:15:58,218 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/ejort/jboss-head/build/output/jboss-5.0.0.Be | ta3/server/default/deploy/app-client.jar | 2007-10-25 15:15:58,218 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Not scheduling removal of context already in error: vfsfile:/home/ejort/jboss-head/bu | ild/output/jboss-5.0.0.Beta3/server/default/deploy/app-client.jar | 2007-10-25 15:15:58,218 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Asked to process() when there is nothing to do. | The last two lines are not true. It needs to uninstall the failed contexts from the Microcontainer. I can reproduce the problem by modifying the HeuristicAllOrNothing test, to validate that a failed deployment doesn't produce an IncompleteDeploymentException after it is undeployed | [ejort@warjort deployer]$ svn diff | Index: test/HeuristicAllOrNothingUnitTestCase.java | =================================================================== | --- test/HeuristicAllOrNothingUnitTestCase.java (revision 66174) | +++ test/HeuristicAllOrNothingUnitTestCase.java (working copy) | @@ -154,6 +154,9 @@ | assertEquals(expectedNothing, deployer2.getDeployedUnits()); | assertEquals(expectedNothing, deployer2.getUndeployedUnits()); | assertEquals(DeploymentState.ERROR, main.getDeploymentState(deployment.getName())); | + | + main.removeDeployment(deployment); | + main.checkComplete(); | } | This test is currently failing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098817#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...