6.5.3 Release Notes

Release Information

Release Date: October 20, 2016

Major Features

Zero-Downtime Upgrade

The Apprenda Installer is now able to upgrade existing Apprenda Platform installations (Platform version 6.5.0 and up) while maintaining hosted guest applications and basic Platform services in a fully-running state.


Minor Features/Improvements

  • Self-signed certificates created by the Apprenda Installer now use the SHA-2 certificate hash algorithm.
  • A warning banner is now displayed in the System Operations Center (SOC) when the license for a given Apprenda installation is exceeded.
  • When patching a guest application in the Developer Portal, users are now redirected to the new promotion report card summary as they are for the application promotion workflow.
  • Apprenda Installer validation has been enhanced to check that RPM installation has succeeded on a Linux node before allowing the addition of that node to the Apprenda Platform.
  • Performance enhancements have been introduced for situations in which the Apprenda Distributed Cache temporarily loses network connectivity.
  • Timeout durations for individual steps in Apprenda Installer workflows are now configurable.


Breaking Changes

Support for the following has been removed as of this release:

  • Public .NET user interface component types and Isolated UI presentation strategy for guest applications
  • Workflows where the Apprenda Installer handles installation of Apprenda to Linux nodes itself (Linux node installation can still be performed manually on a per-node RPM install basis)


Bug Fixes

Apprenda Installer & Upgrade

  • In certain circumstances, a previous attempt to upgrade a Linux node that was part of the Apprenda Platform would leave the node in a state where it would not be able to accept new upgrade initialization trigger requests.
  • When adding one or more Linux nodes to an Apprenda Platform instance using the manual RPM install method, the Java Hosting Enabled setting in the Platform Registry would not automatically be set to True.
  • Adding a trailing slash when defining the Cloud URL during installation of the Apprenda Platform would cause many Platform services to fail to deploy post-install.

System Operations Center (SOC)

  • Because of a caching issue, repeated editing of existing Application Bootstrap Policies in the SOC would cause some information about a given Boostrap Policy to be displayed incorrectly or not be displayed at all.
  • On Apprenda environments which include one or more off-Platform Load Manager nodes, uploading a new Frontend SSL Certificate would fail.
  • Frontend SSL Certificates were not processed correctly when uploaded through the SOC.


  • Improvements have been made to custom credential management within guest application Deployment Manifest data.
  • Apprenda's Cataloging service endpoint has been made more resilient in the face of buffer overflow attacks.
  • Security enhancements were implemented relating to the Repository Browser in the SOC.

Developer Portal and Tools

  • The Apprenda Eclipse plugin would not fail gracefully when the Platform authentication token it was using had expired.
  • When multiple users belonging to the same Apprenda Tenant were logged into the Developer Portal at the same time, if one user was promoting a guest application, the other user was intermittently redirected to that promotion's progress overview.
  • The user securable permission applying to the ability to cancel running guest application promotions was not being honored correctly in the Developer Portal.
  • Under certain circumstances, newly-deployed instances of the Developer Portal UI would not inherit the correct IIS app pool identity.
  • Due to a token-switching issue, the instance token being displayed for a given deployed Add-On instance in the Developer Portal was not correct for the instance.
  • On Hybrid Cloud environments, real-time resource utilization for deployed guest application component workloads would fail to be reported in the Developer Portal if the workloads were hosted on a Cloud that wasn't also hosting the Developer Portal UI.
  • Resource allocation charts in the Developer Portal were not correctly displaying data from deployed guest application Linux Service workloads.

Guest Application Creation and Management

  • The vanity URL setting input for guest applications would not allow inputs of single-element naming, even if the resulting URL was valid.
  • When attempting to patch a guest application's database component, correlated updates using aliases would cause missing object errors during DB script validation.
  • The Apprenda Platform was not displaying memory/CPU utilization statistics for guest application Windows Service component instances.
  • When deleting a guest application, the app's deployed DB instance intermittently would be orphaned, and attempts to recreate an application with the same name would fail to detect the existence of the orphaned DB, leading to an inability to purchase subscriptions for the app.
  • The length limit enforced by the Apprenda Platform for the file path of a guest application being exported through the Developer Portal was too short.
  • In certain circumstances, guest application promotions/demotions would get stuck indefinitely processing, and attempts to cancel the process would have no effect.


  • Issues with the Query Optimator included in MSSQL 2014 caused intermittent timeouts for interactions that the Apprenda Platform had with DB nodes running that SQL version.
  • SSL validation exception handling has been improved to surface more useful errors.
  • Platform Healing sweeps were surfacing timeout errors due to a built-in timeout that was too short but is now configurable.
  • For guest application Java workloads deployed to Red Hat Enterprise Linux 7 nodes, those workloads would in certain circumstances fail to be throttled by resource consumption and/or appear to not be running in the SOC.
  • The GetCustomers() API endpoint did not return some needed information (this issue was introduced in Platform version 6.5.1).
  • For Apprenda environments using an External User Store, if a user belonging to one Apprenda Tenant was added to a second already-existing Tenant, that user would no longer be able to log in.
  • Certain machine configurations backing an Apprenda installation would cause Apprenda's Platform Coordination service to eventually crash.
  • On Apprenda environments with internal encryption enabled, non-default run-as user credentials set for guest application UI components would cause UI deployment failures.