Release Notes

This topic contains the release notes for VMware Tanzu GemFire for Tanzu Application Service (GemFire for Tanzu Application Service).

v2.0.3

Release Date: April 19, 2024

GemFire for Tanzu Application Service v2.0.3:

Runs VMware Tanzu GemFire 10.0.4
Requires the Jammy 1.423 stemcell or a more recent version
Uses JDK 11.0.22
Supports VMware Tanzu Application Service for VMs versions 6.0, 5.0, 4.0, 2.13

Important: The Tanzu GemFire for Redis Apps extension has been removed and is no longer supported.

Reminders about Tanzu GemFire v2.0:

In GemFire for Tanzu Application Service v2.0, JDK was bumped to Java 11 from Java 8 in GemFire for Tanzu Application Service v1.14. If you use custom JVM parameters in advanced Java 8 configurations that are not supported in Java 11, you may see a Service broker error during service instance upgrades. For a workaround, see Service Broker Error in the Known Issues section below.
GemFire for Tanzu Application Service v2.0 added support for Redis configuration options on service instances of GemFire for Tanzu Application Service. For more information about these options, see Service Instance Configuration Parameters in Using the Tanzu GemFire for Redis Apps Extension.

For VMware Tanzu Application Service for VMs and Ops Manager version compatibility, see Product Snapshot and Version Compatibility.

Version 2.0.3 Product Snapshot

Element	Details
Version	2.0.3
Release date	April 19, 2024
Software component version	Tanzu GemFire v10.0.4
Compatible VMware Tanzu Application Service for VMs versions	6.0, 5.0, 4.0, 2.13
Compatible Ops Manager versions	v3.0, v2.10
IaaS support	AWS, Azure, GCP, OpenStack, vSphere
IPsec support	Yes
Required stemcell version	Jammy v1.423 or a more recent version
JDK shipped with Tanzu GemFire	11
Minimum Java buildpack version required for apps	v4.18

Breaking Changes

v2.0.2

Release Date: February 26, 2024

GemFire for Tanzu Application Service v2.0.2:

Runs VMware Tanzu GemFire 10.0.3
Requires the Jammy 1.379 stemcell or a more recent version
Uses JDK 11.0.21
Supports VMware Tanzu Application Service for VMs versions 6.0, 5.0, 4.0, 3.0, 2.13

Reminders about Tanzu GemFire v2.0:

In GemFire for Tanzu Application Service v2.0, JDK was bumped to Java 11 from Java 8 in GemFire for Tanzu Application Service v1.14. If you use custom JVM parameters in advanced Java 8 configurations that are not supported in Java 11, you may see a Service broker error during service instance upgrades. For a workaround, see Service Broker Error in the Known Issues section below.
GemFire for Tanzu Application Service v2.0 added support for Redis configuration options on service instances of GemFire for Tanzu Application Service. For more information about these options, see Service Instance Configuration Parameters in Using the Tanzu GemFire for Redis Apps Extension.

For VMware Tanzu Application Service for VMs and Ops Manager version compatibility, see Product Snapshot and Version Compatibility.

Version 2.0.2 Product Snapshot

Element	Details
Version	2.0.2
Release date	February 26, 2024
Software component version	Tanzu GemFire v10.0.3
Compatible VMware Tanzu Application Service for VMs versions	6.0, 5.0, 4.0, 3.0, 2.13
Compatible Ops Manager versions	v3.0, v2.10
IaaS support	AWS, Azure, GCP, OpenStack, vSphere
IPsec support	Yes
Required stemcell version	Jammy v1.379 or a more recent version
JDK shipped with Tanzu GemFire	11
Minimum Java buildpack version required for apps	v4.18

v2.0.1

Release Date: December 12, 2023

No new features included in this release.

GemFire for Tanzu Application Service v2.0.1:

Runs VMware Tanzu GemFire 10.0.2.RC1
Requires the Jammy 1.309 stemcell or a more recent version
Uses JDK 11.0.21
Supports VMware Tanzu Application Service for VMs versions 5.0, 4.0, 3.0, and 2.13

Reminders about Tanzu GemFire v2.0:

In GemFire for Tanzu Application Service v2.0, JDK was bumped to Java 11 from Java 8 in GemFire for Tanzu Application Service v1.14. If you use custom JVM parameters in advanced Java 8 configurations that are not supported in Java 11, you may see a Service broker error during service instance upgrades. For a workaround, see Service Broker Error in the Known Issues section below.
GemFire for Tanzu Application Service v2.0 added support for Redis configuration options on service instances of GemFire for Tanzu Application Service. For more information about these options, see Service Instance Configuration Parameters in Using the Tanzu GemFire for Redis Apps Extension.

For VMware Tanzu Application Service for VMs and Ops Manager version compatibility, see Product Snapshot and Version Compatibility.

Version 2.0.1 Product Snapshot

Element	Details
Version	2.0.1
Release date	December 12, 2023
Software component version	Tanzu GemFire v10.0.2.RC1
Compatible VMware Tanzu Application Service for VMs versions	5.0, 4.0, 3.0, 2.13
Compatible Ops Manager versions	v3.0, v2.10
IaaS support	AWS, Azure, GCP, OpenStack, vSphere
IPsec support	Yes
Required stemcell version	Jammy v1.309 or a more recent version
JDK shipped with Tanzu GemFire	11
Minimum Java buildpack version required for apps	v4.18

Breaking Changes

No breaking changes in v2.0.1. For v2.0, see v2.0 Breaking Changes.

Known Issues

No new known issues in v2.0.1. See v2.0 Known Issues.

v2.0.0

Release Date: June 14, 2023

Features included in this release:

GemFire for Tanzu Application Service v2.0 upgrades from v1.14.
JDK bumped from Java 8 in GemFire for Tanzu Application Service v1.14 has been bumped to Java 11 in GemFire for Tanzu Application Service v2.0. If you use custom JVM parameters in advanced Java 8 configurations that are not supported in Java 11, you may see a Service broker error during service instance upgrades. For a workaround, see Service Broker Error in the Known Issues section below.
Support for Redis configuration options on service instances of GemFire for Tanzu Application Service. For more information about these options, see Service Instance Configuration Parameters in Using the Tanzu GemFire for Redis Apps Extension.
This version of GemFire for Tanzu Application Service runs Tanzu GemFire 10.0.
This release supports VMware Tanzu Application Service for VMs versions 4.0, 3.0, 2.13, 2.12, and 2.11.

For VMware Tanzu Application Service for VMs and Ops Manager version compatibility, see Product Snapshot and Version Compatibility.

Version 2.0 Product Snapshot

Element	Details
Version	2.0
Release date	June 14, 2023
Software component version	Tanzu GemFire v10.0
Compatible VMware Tanzu Application Service for VMs versions	4.0, 3.0, 2.13, 2.12, 2.11
Compatible Ops Manager versions	v2.10
IaaS support	AWS, Azure, GCP, OpenStack, vSphere
IPsec support	Yes
Required stemcell version	Jammy v1.117 or a more recent version
JDK shipped with Tanzu GemFire	11
Minimum Java buildpack version required for apps	v4.18

Breaking Changes

Metric Keys Renamed

The metric keys listed in Monitoring GemFire for Tanzu Application Service Service Instances have been renamed, with any instance of . replaced by _.

Broker Metrics Renamed

The broker metrics listed in Monitor Quota Use and Service Instance Count in Setting Service Instance Quotas _ have been renamed as follows:

`on-demand-broker/p-cloudcache/quota_remaining`	`_on-demand-broker_p_cloudcache_quota_remaining`
`on-demand-broker/p-cloudcache/PLAN-NAME/quota_remaining`	`_on-demand-broker_p_cloudcache_PLAN-NAME_quota_remaining`
`on-demand-broker/p-cloudcache/total_instances`	`_on-demand-broker_p_cloudcache_total_instances`
`on-demand-broker/p-cloudcache/PLAN-NAME/total_instances`	`_on-demand-broker_p_cloudcache_PLAN-NAME_total_instances`

Known Issues

Service Broker Error

If you use custom JVM parameters in advanced Java 8 configurations that are not supported in Java 11, you may see a the following error during manual service instance upgrades or when running the “Upgrade All Service Instances for VMware GemFire for VMs” errand:

Service broker error: invalid previous JVM configuration options: [<list of JVM options>], please delete or replace them in the previous deployment

Record the to use when working around the issue.

To work around this issue:

In a terminal window, retrieve the manifest for the affected service instance by running the following command:
```
bosh -d service-instance_$(cf service SERVICE-INSTANCE-NAME --guid)   manifest > manifest.yml
```
Where SERVICE-INSTANCE-NAME is the name of the affected service instance.
Edit the manifest.yml file that you just created by removing or replacing with the JDK11 equivalent all of the options in the <list of JVM options> part of the error message. The same option might appear multiple times.
Redeploy the service instance with the modified manifest:
```
bosh -d service-instance_$(cf service SERVICE-INSTANCE-NAME --guid)  deploy manifest.yml
```
Where SERVICE-INSTANCE-NAME is the name of the affected service instance.
Perform the upgrade:
```
cf update-service <service_instace_name> --upgrade
```
Where SERVICE-INSTANCE-NAME is the name of the affected service instance.

Validation Errand Failure

If you are upgrading to GemFire for Tanzu Application Service v2.0, you should first use gfsh to destroy the Lucene indexes on persistent regions before restarting the cluster.

GemFire for Tanzu Application Service v2.0 does not enforce this requirement during the processing of cf update-service <service_instace_name> --upgrade, but it does include a validation errand that is executed before making the upgrade available to developers.

Resolution:

If this errand fails, the errand’s output lists the Service instances that contain indexes that must be deleted before upgrade. Delete these indexes, then run the upgrade process again.

Validation Errand