Release Notes for Session State Caching Powered by GemFire

Overview

Session State Caching Powered by GemFire supports the deployment of Pivotal GemFire to Pivotal Cloud Foundry® (PCF) for the purposes of HTTP session replication, similar to what is provided by the Pivotal GemFire HTTP Session Management Modules in the standalone product.

When you deploy the Session State Caching service, Pivotal Cloud Foundry® automatically configures GemFire and creates regions for HTTP session replication.

Note that the releases below are listed chronologically, starting with the most recent.

Feedback

Please provide any bugs, feature requests, or questions either to Pivotal Customer Support at https://support.pivotal.io or email pivotal-cf-feedback@pivotal.io.

1.2.0.0

Release Date: 2nd June 2016

New in this Release

  • The packaged GemFire is upgraded from 8.2.0.5 to 8.2.1.
  • The enable-network-partition-detection property is now enabled to prevent against data corruption in split-brain scenarios.
  • Cluster stability has been improved during restarts and during service instance deletions.
  • Default timeout of cf restart-gemfire has been increased from 120 seconds to 900 seconds to accommodate slower-than-expected startup of servers and locators.
  • When running on Azure, GemFire servers will have redundancy zones tied directly to Azure’s fault domains so that redundancy for partitioned regions is satisfied across multiple virtual server racks.
  • The cf export-gemfire command now gives feedback about missing arguments, making it easier to export your GemFire logs, cluster configs and properties.

Upgrade Warning: Downtime Required

Upgrading to 1.2.0.0 will require downtime for your Session State Caching Powered by GemFire deployment.

Since the enable-network-partition-detection=true property must be set on the entire cluster at the same time, we are unable to do a rolling upgrade. Previously deployed apps and service instances will continue to function normally after the upgrade, though Session State Caching Powered by GemFire will be unavailable during the upgrade.

For Ops Manager-deployed tiles:

  1. Upload the 1.2.0.0 Session State Caching Powered by GemFire tile to Ops Manager.
  2. Under Available Products > Session State Caching (GemFire), click Add.

    In Ops Manager, add Session State Caching (GemFire)

  3. bosh target your Ops Manager-deployed bosh director.

  4. bosh stop your previously deployed Session State Caching Powered by GemFire tile. This will stop the Session State Caching Powered by GemFire service broker and all service instances.

  5. In Ops Manager, click Apply Changes.

    In Ops Manager, click Apply Changes

For bosh-deployed releases:

  1. bosh upload the releases contained in this tile
  2. bosh stop your existing GemFire deployment
  3. bosh deploy the manifest contained in this tile
  4. bosh start your new deployment

Known Issues and Limitations:

Upgrading to 1.2.0.0 will require downtime for your Session State Caching Powered by GemFire deployment as detailed in the previous section.

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, please update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from 8.0 to 8.2. GemFire 8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack 3.4. This dependency has been included in Java buildpack 3.6.

1.1.10.0

Release Date: 18th February 2016

Note: This release requires Ops Manager and Elastic Runtime 1.6.x.

New in this Release:

  • Updated stemcell to 3146.8, patches CVE-2015-7547 and other Ubuntu CVEs.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, please update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from 8.0 to 8.2. GemFire 8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack 3.4. This dependency has been included in Java buildpack 3.6.

1.1.9.0

Release Date: 3rd February 2016

Note: This release requires Ops Manager and Elastic Runtime 1.6.x.

New in this Release:

  • Updated stemcell to 3146.6, patches Ubuntu CVEs

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, please update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from 8.0 to 8.2. GemFire 8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack 3.4. This dependency has been included in Java buildpack 3.6.

1.1.0.6

Release Date: 28th January 2016

Note: This release requires Ops Manager and Elastic Runtime 1.4.x or 1.5.x.

New in this Release:

  • Updated stemcell to 3146.5, resolves CVE-2016-0728.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, please update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from 8.0 to 8.2. GemFire 8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack 3.4. This dependency has been included in Java buildpack 3.6.

1.1.8.0

Release Date: 21st January 2016

Note: This release requires Ops Manager and Elastic Runtime 1.6.x.

New in this Release:

  • Updated stemcell to 3146.5, resolves CVE-2016-0728.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, please update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from 8.0 to 8.2. GemFire 8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack 3.4. This dependency has been included in Java buildpack 3.6.

1.1.0.5

Release Date: 19th January 2016

Note: This release requires Ops Manager and Elastic Runtime 1.4.x or 1.5.x.

New in this Release:

  • Updated stemcell to 3146.3, resolves CVE-2016-0777 and CVE-2016-0778.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, please update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from 8.0 to 8.2. GemFire 8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack 3.4. This dependency has been included in Java buildpack 3.6.

1.1.7.0

Release Date: 18th January 2016

Note: This release requires Ops Manager and Elastic Runtime 1.6.x.

New in this Release:

  • Updated stemcell to 3146.3, resolves CVE-2016-0777 and CVE-2016-0778.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, please update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from 8.0 to 8.2. GemFire 8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack 3.4. This dependency has been included in Java buildpack 3.6.

1.1.6.0

Release Date: 8th January 2016

Note: This release requires Ops Manager and Elastic Runtime 1.6.x.

New in this Release:

  • Updated stemcell to 3146.2, resolves CVE USN-2857-1.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, please update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from 8.0 to 8.2. GemFire 8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack 3.4. This dependency has been included in Java buildpack 3.6.

1.1.0.4

Release Date: 8th January 2016

Note: This release requires Ops Manager and Elastic Runtime 1.4.x or 1.5.x.

New in this Release:

  • Updated stemcell to 3146.2, resolves CVE USN-2857-1.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, please update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from 8.0 to 8.2. GemFire 8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack 3.4. This dependency has been included in Java buildpack 3.6.

1.1.5.0

Release Date: 3rd December 2015

Note: This release requires Ops Manager and Elastic Runtime 1.6.x.

New in this Release:

  • Security update to stemcell 3146, which fixes USN-2821-1.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, please update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from 8.0 to 8.2. GemFire 8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack 3.4. This dependency has been included in Java buildpack 3.6.

1.1.0.3

Release Date: 3rd December 2015

Note: This release requires Ops Manager and Elastic Runtime 1.4.x or 1.5.x.

New in this Release:

  • Security update to stemcell 3146, which fixes USN-2821-1.
  • Support for the “Trusted Certificates” feature in Ops Manager. The certificates from “Trusted Certificates” are deployed to all GemFire nodes, and to the GemFire service broker.

    Note on self-signed and internal CA signed certificates: If you are using a self-signed certificate or a certificate signed by an internal or other not known certificate authority (CA), you must add the certificate (or certificate chain) to the “Trusted Certificates” in Ops Manager.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

There is a known issue where apps fail to stage when using the Java buildpacks 3.4.x and 3.5.x. To resolve this, please update Java buildpack to 3.6. In Java buildpack 3.4, GemFire was upgraded from 8.0 to 8.2. GemFire 8.1 introduced a dependency on log4j, but log4j was not added to the Java buildpack 3.4. This dependency has been included in Java buildpack 3.6.

1.1.4.0

Release Date: 1st December 2015

Note: This release requires Ops Manager and Elastic Runtime 1.6.x.

New in this Release:

  • Security update to stemcell 3144, which fixes USN-2815-1, USN-2812-1 and USN-2810-1.
  • Support for the “Trusted Certificates” feature in Ops Manager. The certificates from “Trusted Certificates” are deployed to all GemFire nodes, and to the GemFire service broker.

    Note on self-signed and internal CA signed certificates: If you are using a self-signed certificate or a certificate signed by an internal or other not known certificate authority (CA), you must add the certificate (or certificate chain) to the “Trusted Certificates” in Ops Manager.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

1.1.3.0

Release Date: 11th November 2015

Note: This release requires Ops Manager and Elastic Runtime 1.6.x.

New in this Release:

  • Security update to stemcell 3130, which fixes USN-2806-1 and USN-2798-1.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

1.1.0.2

Release Date: 11th November 2015

Note: This release requires Ops Manager and Elastic Runtime 1.4.x or 1.5.x.

New in this Release:

  • Security update to stemcell 3130, which fixes USN-2806-1 and USN-2798-1.

Known Issues and Limitations:

See Known Issues and Limitations for release 1.1.0.0, below.

1.1.2.0

Release Date: 3rd November 2015

Note: This release requires Ops Manager and Elastic Runtime 1.6.x.

New in this Release:

  • Security update, stemcell 3112.
  • Fix for the issue of Internet access being required during installation, found in version 1.1.1.0.

Known Issues and Limitations:

See Known Issues and Limitations for the previous release, 1.1.0.0, below.

1.1.0.1

Release Date: 3rd November 2015

Note: This release requires Ops Manager and Elastic Runtime 1.4.x or 1.5.x.

New in this Release:

  • Security update, stemcell 3112, for Ops Manager and Elastic Runtime 1.4.x, 1.5.x

Known Issues and Limitations:

See Known Issues and Limitations for the previous release, 1.1.0.0, below.

1.1.1.0

Release Date: 26th October 2015

New in this Release:

  • Support for Elastic Runtime 1.6.
  • Stemcell 3100.

Known Issues and Limitations:

See Known Issues and Limitations for the previous release, 1.1.0.0, below.

1.1.0.0

Release Date: 7th October 2015

New in this Release:

  • Stemcell 3094 (regular security upgrade).
  • Support for HTTPS only traffic to HAProxy. This release supports disabling HTTP traffic to both UAA and HAProxy
  • Upgraded Pivotal GemFire to version 8.2
  • Upgraded Java to version 8, and JRE 1.8
  • Drain script improvements
  • Improved handling of self-signed certificates
  • Fixed the issue of spaces in the name of the service plan causing the service errand “Service Offering Smoke Test” to fail.

Known Issues and Limitations:

  • On AWS, only deployments to the US-East region are supported. Pivotal is working to provide multi-region support in a future release.
  • The service supports only a single Pivotal Cloud Foundry® availability zone. Although the service enables GemFire HA features such as redundancy and persistence, a failure of the targeted availability zone can result in the loss of session state data.

    Note: If there is more than one available zone, you may see deployment failures or uneven sized clusters.

  • Elastic scaling is not supported. The number of locators and cache servers allowed per GemFire instance (cluster) is fixed at 2 and 3 respectively. If you fail to define a ratio of 2:3 locators to cache servers in the resources tab of the Service tile in Ops Manager, deployment of the service will fail.

  • If you deploy the service and then subsequently reduce the number of clusters, all allocated instances are destroyed.

  • GemFire WAN replication is not supported.

1.0.2.0

Release Date: 1st September 2015

New in this Release:

  • Stemcell 3062. This is a regular security upgrade that resolves the following issues:
    • [USN-2694-1] PCRE vulnerabilities
    • [USN-2698-1] SQLite vulnerabilities
    • [USN-2710-1] OpenSSH vulnerabilities
    • [USN-2710-2] OpenSSH regression
    • [USN-2718-1] Linux kernel (Vivid HWE) vulnerability
  • Fix an issue identified in the 1.0.1.0 release where Pulse denied access after a service instance upgrade.

Known Issues and Limitations:

  • Experimental feature HTTPS traffic to HAProxy not supported

1.0.1.0

Release Date: 4th August 2015

New in this Release:

  • Stemcell 3026 (resolves CVE-2015-3290)

  • Support for the experimental feature HTTPS traffic to UAA

Known Issues and Limitations:

  • Experimental feature HTTPS traffic to HAProxy not supported
  • For the running service instances that are upgraded from 1.0.0, Pulse starts to deny access upon upgrade with a cross-site request forgery (CSRF) related error. Service instances created upon upgrade are not affected.

1.0.0.0

Release Date: 1st July 2015

New in this Release

  • This is the inital General Availability release

  • Includes GemFire 8.1.0.5

  • 3 data server VM’s and 2 locator VM’s per service instance (cluster)

  • A dedicated VM per node (a service instance gets 5 dedicated nodes, 3 servers and 2 locators)

  • Out of the box configuration for Tomcat container in the java buildpack

Known Issues and Limitations

  • On AWS, this version of the product supports deployments only to the US-East region. Pivotal is working to provide multi-region support in a future release.

  • The experimental HTTPS-only feature in Elastic Runtime 1.5 may cause issues with this version of the product. Pivotal is working to provide full support for HTTPS-only traffic in a future release.

    Note: BOSH Stemcell 2865.1 is required for installation on Ops Manager 1.5.x and above.

  • The service supports only a single Pivotal Cloud Foundry® availability zone. Although the service enables GemFire HA features such as redundancy and persistence, a failure of the targeted availability zone can result in the loss of session state data.

    Note: If there is more than one available zone, you may see deployment failures or uneven sized clusters.

  • Elastic scaling is not supported. The number of locators and cache servers allowed per GemFire instance (cluster) is fixed at 2 and 3 respectively. If you fail to define a ratio of 2:3 locators to cache servers in the resources tab of the Service tile in Ops Manager, deployment of the service will fail.

  • If you deploy the service and then subsequently reduce the number of clusters, all allocated instances are destroyed.

  • GemFire WAN replication is not supported.

  • If spaces are used in the name of the service plan, the service errand “Service Offering Smoke Test” fails, and the service installation fails as a result. To avoid this, you can either avoid using spaces in the name of the service plan, or uncheck the service errand “Service Offering Smoke Test”.

Create a pull request or raise an issue on the source for this page in GitHub