KB-2070 "Another deployment is already running" when attempting to deploy using the Automated Deployment Manager (ADM)

Parmida Borhani — Thu, 30 Jan 2020 23:21:37 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 1/30/2020 11:21:37 PM

Symptoms

While inspecting or importing a package using the Automated Deployment Manager (ADM) servlet, the status will remain on "In Progress" indefinitely. This looks like:

In the application server logs, the following error output will appear:

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.DeploymentUtils - Error starting the deployment. Another deployment is already running.

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet - Error while initializing the deployment.
java.lang.IllegalStateException: Error starting the deployment. Another deployment is already running.
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.validateNonConcurrentDeployment(DeploymentUtils.java:409)
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.startDeployment(DeploymentUtils.java:148)
        at com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet.doPost(RemoteDeploymentAutomationServlet.java:111)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
        at com.atlassian.plugin.servlet.DelegatingPluginServlet.service(DelegatingPluginServlet.java:37)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)

Cause

In the most common instance, this means that an action has been attempted while the ADM is already processing a deployment. It can also be observed after an inspect failure against the deployment package has occurred.

Action

Check the application server logs to ensure that the behavior is in line with this article and not KB-1445.
Confirm that any expected deployments have completed. KB-1738 provides steps on how to check if an application import was successful.
Remove the deployment_progress_file.properties file located in the All Objects > Default Community > Temporary Documents Knowledge Center > Temporary Documents folder.
Re-attempt the deployment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: ADM, plug-ins, Devops: Infrastructure, deploy, import/export, plugins

KB-2070 "Another deployment is already running" when attempting to deploy using the Automated Deployment Manager (ADM)

Parmida Borhani — Thu, 30 Jan 2020 23:21:37 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 1/30/2020 11:21:37 PM

Symptoms

While inspecting or importing a package using the Automated Deployment Manager (ADM) servlet, the status will remain on "In Progress" indefinitely. This looks like:

In the application server logs, the following error output will appear:

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.DeploymentUtils - Error starting the deployment. Another deployment is already running.

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet - Error while initializing the deployment.
java.lang.IllegalStateException: Error starting the deployment. Another deployment is already running.
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.validateNonConcurrentDeployment(DeploymentUtils.java:409)
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.startDeployment(DeploymentUtils.java:148)
        at com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet.doPost(RemoteDeploymentAutomationServlet.java:111)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
        at com.atlassian.plugin.servlet.DelegatingPluginServlet.service(DelegatingPluginServlet.java:37)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)

Cause

Action

Check the application server logs to ensure that the behavior is in line with this article and not KB-1445.
Confirm that any expected deployments have completed. KB-1738 provides steps on how to check if an application import was successful.
Remove the deployment_progress_file.properties file located in the All Objects > Default Community > Temporary Documents Knowledge Center > Temporary Documents folder.
Re-attempt the deployment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: ADM, Devops: Infrastructure, deploy, import/export, shared components, plugins

KB-XXXX "Another deployment is already running" when attempting to deploy using the Automated Deployment Manager (ADM)

Parmida Borhani — Thu, 30 Jan 2020 05:53:00 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 1/30/2020 5:53:00 AM

Symptoms

While inspecting or importing a package using the Automated Deployment Manager (ADM) servlet, the status will remain on "In Progress" indefinitely. This looks like:

In the application server logs, the following error output will appear:

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.DeploymentUtils - Error starting the deployment. Another deployment is already running.

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet - Error while initializing the deployment.
java.lang.IllegalStateException: Error starting the deployment. Another deployment is already running.
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.validateNonConcurrentDeployment(DeploymentUtils.java:409)
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.startDeployment(DeploymentUtils.java:148)
        at com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet.doPost(RemoteDeploymentAutomationServlet.java:111)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
        at com.atlassian.plugin.servlet.DelegatingPluginServlet.service(DelegatingPluginServlet.java:37)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)

Cause

Action

Check the application server logs to ensure that the behavior is in line with this article and not KB-1445.
Confirm that any expected deployments have completed. KB-1738 provides steps on how to check if an application import was successful.
Remove the deployment_progress_file.properties file located in the All Objects > Default Community > Temporary Documents Knowledge Center > Temporary Documents folder.
Re-attempt the deployment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: ADM, Devops: Infrastructure, deploy, import/export, shared components, plugins

KB-XXXX "Another deployment is already running" when attempting to deploy using the ADM

Tristan Newmann — Thu, 30 Jan 2020 05:00:50 GMT

Revision 3 posted to Appian Knowledge Base by Tristan Newmann on 1/30/2020 5:00:50 AM

Symptoms

While inspecting or importing a package using the Automated Deployment Manager (ADM) servlet, the status will remain on "In Progress" indefinitely. This looks like:

In the application server logs, the following error output will appear:

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.DeploymentUtils - Error starting the deployment. Another deployment is already running.

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet - Error while initializing the deployment.
java.lang.IllegalStateException: Error starting the deployment. Another deployment is already running.
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.validateNonConcurrentDeployment(DeploymentUtils.java:409)
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.startDeployment(DeploymentUtils.java:148)
        at com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet.doPost(RemoteDeploymentAutomationServlet.java:111)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
        at com.atlassian.plugin.servlet.DelegatingPluginServlet.service(DelegatingPluginServlet.java:37)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)

Cause

Action

Check the application server logs to ensure that there isn't another error resulting in this behaviour.
Confirm that any expected deployments have completed (by checking the Tempo news feed) or failed (verify by checking the application server log).
Remove the deployment_progress_file.properties file located in the All objects > Default Community > Temporary Documents Knowledge Center > Temporary Documents folder.
Re-attempt the deployment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: ADM, Devops: Infrastructure, deploy, import/export, shared components, plugins

KB-XXXX "Another deployment is already running" when attempting to deploy using the ADM

Tristan Newmann — Thu, 30 Jan 2020 05:00:09 GMT

Revision 2 posted to Appian Knowledge Base by Tristan Newmann on 1/30/2020 5:00:09 AM

Symptoms

While inspecting or importing a package using the Automated Deployment Manager (ADM) servlet, the status will remain on "In Progress" indefinitely. This looks like:

In the application server logs, the following error output will appear:

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.DeploymentUtils - Error starting the deployment. Another deployment is already running.

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet - Error while initializing the deployment.
java.lang.IllegalStateException: Error starting the deployment. Another deployment is already running.
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.validateNonConcurrentDeployment(DeploymentUtils.java:409)
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.startDeployment(DeploymentUtils.java:148)
        at com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet.doPost(RemoteDeploymentAutomationServlet.java:111)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
        at com.atlassian.plugin.servlet.DelegatingPluginServlet.service(DelegatingPluginServlet.java:37)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)

Cause

Action

Check the application server logs to ensure that there isn't another error resulting in this behaviour.
Confirm that any expected deployments have completed (by checking the Tempo news feed) or failed (verify by checking the application server log).
Remove the deployment_progress_file.properties file location in the All objects > Default Community > Temporary Documents Knowledge Center > Temporary Documents folder.
Reattempt the deployment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: ADM, Devops: Infrastructure, deploy, import/export, shared components, plugins

KB-XXXX "Another deployment is already running" when attempting to deploy using the ADM

Tristan Newmann — Thu, 30 Jan 2020 04:59:19 GMT

Revision 1 posted to Appian Knowledge Base by Tristan Newmann on 1/30/2020 4:59:19 AM

Symptoms

While inspecting or importing a package using the Automated Deployment Manager (ADM) servlet, the status will remain on "In Progress" indefinitely. This looks like:

In the application server logs, the following error output will appear:

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.DeploymentUtils - Error starting the deployment. Another deployment is already running.

YYYY-MM-DD HH:MM:SS,sss [ajp-nio-8009-exec-XXX] ERROR com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet - Error while initializing the deployment.
java.lang.IllegalStateException: Error starting the deployment. Another deployment is already running.
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.validateNonConcurrentDeployment(DeploymentUtils.java:409)
        at com.appiancorp.ps.plugins.automatedimport.DeploymentUtils.startDeployment(DeploymentUtils.java:148)
        at com.appiancorp.ps.plugins.automatedimport.remote.RemoteDeploymentAutomationServlet.doPost(RemoteDeploymentAutomationServlet.java:111)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
        at com.atlassian.plugin.servlet.DelegatingPluginServlet.service(DelegatingPluginServlet.java:37)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)

Cause

Action

Check the application server logs to ensure that there isn't another error resulting in this behaviour.
Confirm that any expected deployments have completed (by checking the Tempo news feed) or failed (verify by checking the application server log).
Remove the deployment_progress_file.properties file location in the All objects > Default Community > Temporary Documents Knowledge Center > Temporary Documents folder.
Reattempt the deployment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: ADM, Devops: Infrastructure, deploy, import/export, shared components, plugins