11.4 Application management exceptions

Table 10 Application management exceptions

•ApplicationDisableException: Indicates that an application cannot be disabled.

◦Occurs when an app is STAGED or UPGRADE_STAGED, or something else has gone wrong (specified in error message)

◦HTTP code: 500

•ApplicationEnableException: Indicates that an application cannot be enabled.

◦Occurs when an app is not DISABLED, or something else has gone wrong (as specified in the error message).

◦HTTP code: 500

•ApplicationInstallException: Indicates that an app cannot be installed.

◦Occurs when an application is not STAGED, or something else has gone wrong (as specified in the error message).

◦HTTP code: 500

•ApplicationStartException: Indicates that an application cannot be started.

◦Occurs when an app is not RESOLVED, or something else has gone wrong (as specified in the error message).

◦HTTP code: 500

•ApplicationStopException: Indicates that an app cannot be stopped.

◦Occurs when an application is not ACTIVE, or something else has gone wrong (as specified in the error message).

◦HTTP code: 500

•ApplicationUninstallException: Indicates that an application cannot be uninstalled.

◦Occurs when something has gone wrong as (as specified in the error message).

◦HTTP code: 500

•ApplicationUpgradeException: Indicates that an application cannot be upgraded.

◦Occurs when an application is not UPGRADE_STAGED, or that something has gone wrong (as specified in the error message).

◦HTTP code: 500

•ApplicationUploadException: Indicates that an application cannot be uploaded to the controller.

◦Seen when an IO error occurs while uploading the application to the controller.

◦HTTP code: 500

•ApplicationValidationException: Indicates that an application zip file fails validation. Validation can be from file format to invalid contents to failed signed jar verification (if enabled).

◦HTTP code: 400

102 Troubleshooting