Pivotal GemFire Release Notes
Pivotal GemFire 9.6 is based on Apache Geode version 1.7. Pivotal GemFire 9.6 and Apache Geode share a common set of documentation. Therefore, references to both GemFire and Apache Geode appear throughout this documentation; consider them equivalents.
Pivotal GemFire 9.6 includes the following improvements:
- A pair of new gfsh commands were added in support of cluster configuration:
This Pivotal GemFire 9.6 release includes GemFire-Greenplum Connecter version 3.3. See the GemFire-Greenplum Connecter Release Notes for details.
You can download Pivotal GemFire 9.6 from the Pivotal GemFire product download page.
For details on how to install Pivotal GemFire 9.6, see Installing Pivotal GemFire.
Note that the file name extension for the compressed TAR file is
.tar.gz (rather than
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
geode.disallow-internal-messages-without-credentials system property set to
gfsh>start server --name=server_name --dir=server_config_dir \ --J=-Dgeode.disallow-internal-messages-without-credentials=true
The GemFire 9.6 release is based on the Apache Geode 1.7 release. This section describes issue resolutions that significantly affect GemFire applications. For a list of all issues resolved in Geode 1.7, see the Geode 1.7 Release Notes. Ticket numbers of the form GEODE‑NNNN can be inspected at the Apache Software Foundation site for Geode issues.
GEODE-4218: In the gfsh
start locator command, the deprecated
load-cluster-configuration-from-dir option is no longer required when setting
GEODE-4990, GEM-1991: Fixed a bug that could lead to a null-pointer error (NPE) when starting a server if the cluster configuration service is enabled and the locator hasn’t finished the startup.
GEODE-5157, GEM-2167, GEM-2168, GEM-2169: Fixed a bug that sometimes prevented ClientHealthStats from being propagated when the system has a hostname.
GEODE-5194: Allow gfsh clients with different patch versions to connect to a the same locator.
import cluster-configuration and
export cluster-configuration gfsh commands.
GEODE-5220, GEM-1938: Fixed a bug that could leave a replicated region in an inconsistent state during creation when a parallel async-event-queue or gateway-sender is assigned to it.
GEODE-5230: Fixed a bug that resulted in broken Pulse functionality when SSL was enabled for JMX access.
GEODE-5247: Fixed a bug that resulted in some gfsh data commands displaying an object reference instead of a proper JSON object when returning nested objects.
GEODE-5256, GEM-2076: Parameters passed to the gfsh
start server command now take precedence over defaults and values specified in cache.xml configurations.
GEODE-5433, GEM-2151: Fixed a bug that allowed OQL indexes to retrieve stale data while a region GII update is in progress.
GEODE-5478, GEM-2165: Fixed a bug that caused the
lowRedundancyBucketCount statistic not to be maintained properly when multiple members are stopped and restarted.
GEODE-5534: Fixed a bug that could lead to increased memory usage when PDX values are stored and compression is enabled.
GEODE-5571, GEM-2176: Pulse now shows all data queries, including failed ones.
GEODE-5618, GEM-2206: Fixed a bug that prevented clients with multiuser-authentication enabled from executing functions on particular servers or regions.
GEODE-5631, GEM-2195: Fixed a bug that could lead to increased memory footprint when using asynchronous event listeners.
GEM-2228 Fixed a problem that could cause data inconsistencies between WAN sites with serial gateway senders and multiple writers when operations were applied out of order.
The HTTP session module creates its region that holds metadata on only one server within a cluster. The region needs to be hosted on all the servers.
To correct the issue on a running cluster, connect to the cluster
and run a single
to create the metadata region on all servers.
The command has the form:
create region --name=REGION-NAME --type=REGION-SHORTCUT \ --enable-statistics \ --entry-idle-time-custom-expiry=org.apache.geode.modules.util.SessionCustomExpiry
context.xml file sets the metadata region’s name,
substitute the name for
regionAttributesId in a
context.xml file defines a
substitute its value for
REGION-SHORTCUT in the
create region command.
See Changing the Default GemFire Configuration in the Tomcat Module
for details on the
If the metadata region’s name or type is not set within a
then use a
and use a
Using these defaults results in the
gfsh>create region --name=gemfire_modules_sessions --type=PARTITION_REDUNDANT \ --enable-statistics \ --entry-idle-time-custom-expiry=org.apache.geode.modules.util.SessionCustomExpiry
You can verify that the region is hosted on all servers with the
gfsh>describe region --name=gemfire_modules_sessions
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.