LATEST VERSION: 9.7.2 - RELEASE NOTES
Pivotal GemFire® v9.7

Pivotal GemFire Release Notes

Pivotal GemFire 9.7 is based on Apache Geode version 1.8. Pivotal GemFire 9.7 and Apache Geode share a common set of documentation. Therefore, references to both GemFire and Apache Geode appear throughout this documentation; consider them equivalents.

GemFire v9.7.2 is a patch release for GemFire v9.7 customers that incorporates improvements and bug fixes, particularly with regard to recovery following unexpected network disconnections.

For more information on issues resolved in GemFire v9.7.2, see Issues Resolved in Pivotal GemFire 9.7.2.

What’s New in Pivotal GemFire 9.7

Pivotal GemFire 9.7 includes the following improvements:

  • GemFire clients support trust and keystore rotation
  • Endpoint validation during SSL handshake is enabled
  • Improved latency characteristics of Serial Gateway Sender Queues
  • Function security is dynamically determined by function arguments
  • Added support for Tomcat 9
  • gfsh command hints are now case-independent

Pivotal GemFire 9.7 Breaking Change

GEODE 5861: The configuration options for JNDI bindings have changed, whether configured through XML or gfsh create jndi-binding:

  • The --jdbc-driver-class option is now optional.
  • --url is an alias for the --connnection-url option.
  • The --type option now defaults to SIMPLE.
  • The --type=POOLED option defaults to creating a Hikari pool. Or, implement org.apache.geode.datasource.PooledDataSourceFactory to customize the class that implements the pool.

The breaking change represents a rare use case. The change is that a custom class that implements the pool must now implement the org.apache.geode.datasource.PooledDataSourceFactory interface.

Installing Pivotal GemFire 9.7

You can download Pivotal GemFire 9.7 from the Pivotal GemFire product download page.

For details on how to install Pivotal GemFire 9.7, see Installing Pivotal GemFire.

Upgrading to Pivotal GemFire 9.7

To upgrade from an earlier version of GemFire to the current version, see Upgrading Pivotal GemFire.

When servers are upgraded to this GemFire version from a version prior to version 9.1.1, their authentication of client messages is disabled in order to facilitate rolling upgrades. If your clients are set up to send authenticated messages, the servers will honor those messages, but will not enforce authentication until you reinstate authentication on each of the upgraded servers.

To reinstate secure client/server messaging, restart each server with the geode.disallow-internal-messages-without-credentials system property set to true. For example:

gfsh>start server --name=server_name --dir=server_config_dir \
--J=-Dgeode.disallow-internal-messages-without-credentials=true

Resolved Issues

The GemFire 9.7 release is based on the Apache Geode 1.8 release. This section describes issue resolutions that significantly affect GemFire applications. For a list of all issues resolved in Geode 1.8, see the Geode 1.8 Release Notes. Ticket numbers of the form GEODE‑NNNN can be inspected at the Apache Software Foundation site for Geode issues.

Issues Resolved in Pivotal GemFire 9.7.2

GEODE-6244: Fixed a case in which a slowly responding member could mistakenly initiate disconnection of a better-responding member.

GEODE-6271, GEM-2356: Improved support of clients connected to multiple distributed systems by copying serialized types between clusters.

GEODE-6369: Terminate auto-reconnect attempts if reconnect is not possible.

GEODE-6309, GEODE-6363: Restarting locator tries harder to find an existing cluster coordinator before assuming the role itself.

GEODE-6423, GEM-2410: Availability check following a network outage honors member timeout setting before disconnecting.

GEODE-6451, GEODE-6522: Fixed a membership issue that could cause the server to hang during shutdown.

GEODE-6488, GEM-2400: Improved handling of query tasks so timed-out queries can be re-executed and multiple cancellation tasks will not be ignored.

Issues Resolved in Pivotal GemFire 9.7.1

GEODE-92: Fixed a bug in which custom expiry code that called getValue() could cause a deadlock that resulted in no region operations completing. The previous fix for GEODE-92 did not cover all possibilities.

GEODE-5747, GEODE-6065: Improved the WAN gateway sender’s resilience in the face of intermittent DNS failures or unexpected socket resets in the underlying operating system.

GEODE-6177: Improved the gateway sender’s ability to re-authenticate upon reconnection following a dropped WAN connection.

GEODE-6215, GEM-2341: Fixed a bug with the HTTP session store that resulted in the session region not being created on all servers.

GEODE-6267, GEODE-6287, GEM-2352: Fixed server side memory leaks that occurred during client departure.

GEODE-6328, GEODE-6329, GEM-2376: Fixed issues with the gfsh show missing-disk-stores command, in which the command listed instances that were not missing or duplicate entries.

GEODE-6344, GEM-2365: Fixed a source of spurious “socket read timeout” exceptions on client proxy reconnection requests by replacing existing proxies with new instances.

Issues Resolved in Pivotal GemFire 9.7.0

GEODE-5857, GEM-2233: Resolved some race conditions in JMX registration during startup and shutdown.

GEODE-5861: JDBC Connector now uses gfsh jndi-binding instead of jdbc-connection.

GEODE-5925, GEM-2262: Fixed an issue where AcceptorImpl was sending out unnecessary profile update messages during cache closure operations.

GEODE-6078, GEM-2265: Use of Pool APIs for doing operations when multiuser-secure-mode-enabled is set to true no longer causes a java.lang.UnsupportedOperationException.

Support

General support includes security vulnerability resolutions and critical bug fixes in all supported minor versions, while other maintenance is applied only to the latest supported minor release.

Obtaining and Installing Security Updates

New versions of Pivotal GemFire often include important security fixes, so Pivotal recommends you keep up to date with the latest releases.

For details about any security fixes in a particular release, see the Pivotal security page.