Pivotal Cloud Cache Release Notes

Warning: Pivotal Cloud Cache v1.7 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.


Release Date: July 24, 2019

Features included in this release:

  • The PCC smoke test no longer fails when HTTP is disabled in the Pivotal Cloud Foundry (PCF) environment.
  • PCC now runs Pivotal GemFire 9.7.2.
  • This version adds support for Pivotal Application Service (PAS) 2.6.


Release Date: April 30, 2019

Features included in this release:

  • PCC permits authentication and authorization using your enterprise single sign-on system, such as LDAP.
  • PCC requires TLS encryption for using gfsh and Pulse. Follow the instructions in Preparing for TLS to set up TLS encryption.
  • WARNING: Follow the procedure detailed in Special Upgrade Procedure for Dev and Small Footprint Plans when upgrading from PCC v1.6.x for plans that colocate system components on a single VM. This applies to the dev plan and to the small footprint plan.

  • The new ReplyWaitsInProgress metric allows operators to identify unhealthy cluster members or network connectivity issues.
  • If a ClamAV or File Integrity Monitor is detected, available memory for GemFire servers is reduced to allow enough memory for these PCF add-ons. This prevents a failure during PCC service instance creation.
  • The small footprint plan may be scaled up and down, and metrics are available.
  • Simplified TLS setup for Spring Boot applications, as detailed in Developing an App Under TLS.
  • Metrics can be generated for a single PCC service instance, and are available with log-cache.
  • PCC now ships with JDK 1.8_192.
  • PCC now runs Pivotal GemFire 9.7.1.
  • PCC now supports Pivotal Application Service (PAS) 2.5.

Known Issues

  • Current versions of the Cloud Foundry Command Line Interface (CLI) tool have a known bug that omits the documentation URL when using the cf service command.