An application deployment is in progress indefinitely and does not show either a pass or fail deployment status.


Deployment is running indefinitely. This problem does not generate an error message.


Th process may be hung for some reason. There may be a loss of connection with the Tomcat service, the server restarts during a deployment process, or the agent bootstrap fails.

This problem does not occur for all connection failures. It happens based on the state of the deployment when the connection failure occurred.


If the deployment status does not change to STOPPED in a reasonable amount of time, the process may be hung, in which case you can force a hard stop by clicking Stop again. Clicking Stop a second time forces the deployment to stop immediately without completing the normal sequence of events employed by the stop process. You are prompted to confirm this action by clicking OK. Only force the process to stop if the deployment status has not changed to STOPPED after an unreasonably long time.

When you stop a deployment normally, currently running processes are stopped gracefully. When you force a stop, the deployment is stopped abruptly and currently running processes remain running. In either case, the associated VMs are not cleaned up.


  1. Expand the Execution Plan status window on the deployment summary page.
  2. Diagnose the cause of the long-running task and fix the application blueprint or network connectivity problems.
  3. If the problem persists, stop the deployment by clicking Stop and waiting for the deployment status to change to STOPPED.

    This action gracefully stops the deployment and its related processes and marks the deployment as failed without stopping provisioning so that you can interact with the application. See Using Application Services.

  4. If the deployment fails to stop (fails to return a STOPPED status) within a reasonable amount of time, you can force the deployment to stop by clicking Stop again and confirming the action when prompted.

    This action immediately stops the deployment and leaves its associated processes running.

  5. If the problem is intermittent, you can tear down the failed deployment from the cloud.

    See Using Application Services.