This is documentation for Apprenda 7 and 8.
Documentation for newer version is available at https://new.docs.apprenda.com.

Troubleshooting Failed Deployments

In some cases, a deployed workload may stop unexpectedly (e.g., the process is killed) or fail to deploy due to configuration issues (e.g., it is deployed to the wrong Java version). In order to help Platform Operators troubleshoot these unexpected workload failures, the Platform retains a snapshot of the file system instance directory for failed workloads for the following types of components:

WCF Services

When a WCF service is deployed to a Windows server on the Platform, its binaries are copied to an instance-specific folder (identified by a GUID) located within the ApprendaPlatform\Container\LaunchPads directory (on whichever drive was selected for Apprenda artifacts at installation). When a WCF service workload fails unexpectedly, the folder is moved to the ApprendaPlatform\Container\FailedLaunches directory on that server.

In order to prevent an unexpected accumulation in the FailedLaunches directory, the Platform will retain only a certain number of the most recent folders in the FailedLaunches directory as determined by the value configured for the Deployment.FailedInstanceMaxBackups setting in the Platform Registry.

Java Web Applications (WARs)

When a WAR workload is deployed to a Linux Server on the Platform, its binaries are copied to an instance-specific folder (identified by a GUID) located within the /apprenda/instances directory. When a WAR workload fails unexpectedly, the folder is copied to the /apprenda/failedinstances directory on that server.

In order to prevent an unexpected accumulation in the FailedLaunches directory, the Platform will retain only a certain number of the most recent folders in the failedinstances directory as determined by the value configured for the Deployment.FailedInstanceMaxBackups setting in the Platform Registry.