Pivotal GemFire Release Notes
Pivotal GemFire 9.8 is based on Apache Geode version 1.9. Pivotal GemFire 9.8 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.8.4 is a maintenance release that resolves a variety of issues—see Issues Resolved in Pivotal GemFire 9.8.4 for more information.
Some of the issues addressed in this release resulted in the introduction of new capabilities:
The ability to specify that when an asynchronous event queue (AEQ) first starts, event processing should be paused. A
resumecommand is provided to start event processing at the desired time.
The ability to replace Log4j with an alternative logging scheme
Pivotal Gemfire 9.8.4 includes new
gfsh commands for creating or altering asynchronous event queues (AEQs) such that event processing is not immediately activated at
AEQ creation or restart, but instead is paused until instructed to resume.
See the relevant gfsh Command Help entries for usage details:
create async-event-queue --pause-event-processing(=value)
true, creates an AEQ in which event processing is paused.
alter async-event-queue --pause-event-processing(=value)
true, instructs an existing AEQ to pause event processing the next time the queue restarts. Does not alter behavior of the currently executing AEQ.
Instructs an AEQ to begin event processing.
This release also introduces a related property,
pause-event-processing, for the
<async-event-queue> element in
See <async-event-queue> for details.
A logging framework is broken out into two pieces: the API and the backend.
The API provides the logger API for statements such as
logger.info("Something happened here").
The backend provides appenders for writing those log statements to various destinations such as files, databases, logging servers, etc.
GemFire normally uses
log4j-api for the logger API and
log4j-core for logging to and rolling the
GemFire log file.
Spring Boot and various libraries used by GemFire use
slf4j for the logger API.
To accommodate such alternatives, GemFire automatically includes the jar(s) to redirect
slf4j log statements to the Log4j backend,
log4j-core, so they
get included in the GemFire log file.
If you also wish to use an alternative backend for logging, exclude
log4j-core from your classpath.
Pivotal GemFire 9.8 includes the following improvements:
- Open JDK 11 compatibility
- Reduce the overhead of internal statistics collection resulting in near linear scaling of updates. As a result, most apps should notice increased throughput of local get operations.
- Improvements to recovery following unexpected network disconnections
- Improvements to jndi-binding commands
- Protections against Java and Native clients accessing internal regions inappropriately
- Ability to configure appenders in log4j2.xml
You can download Pivotal GemFire 9.8 from the Pivotal GemFire product download page.
For details on how to install Pivotal GemFire 9.8, see Installing Pivotal GemFire.
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.8 release is based on the Apache Geode 1.9 release. This section describes issue resolutions that significantly affect GemFire applications. For a list of all issues resolved in Geode 1.9, see the Geode 1.9 Release Notes. Ticket numbers of the form GEODE‑NNNN can be inspected at the Apache Software Foundation site for Geode issues.
GEODE-2644, GEODE-6122, GEODE-7050, GEODE-7058, GEM-2259: Made Log4j optional.
GEODE-7079: Fixed a restart timing issue that could occur when Asynchronous Event Distribution and Conflation are in effect.
GEODE-7080, GEM-2648: Fixed a bug in which export of an offline snapshot could fail if a deleted entry was detected in the region.
GEODE-7085: Allow extremely large region version values (greater than Integer.MAX_VALUE) when recovering from disk.
GEODE-7178: Restored the server’s compatibility with Native Client version 9.2+ ‘destroy’ operations, which had been inadvertently disabled in earlier versions of 9.8.
GEODE-7208, GEM-2698: Improved serialization to better support Lucene indexing on inherited fields.
GEM-2588: Fixed a performance issue resulting from a problem in peer-to-peer SSL communication
when the cluster was configured with
conserve-sockets disabled. This fix reverted a change from v9.8.0, GEM-2408/GEODE-6389.
GEODE-6651: Fixed a null-pointer error that occurred with transaction reads on partitioned regions.
GEODE-6721/GEM-2506: Corrected the behavior of the gfsh start locator command to honor a request specifying the secondary IP, instead of always using the host’s primary IP address.
GEODE-6806, GEM-2545: Improved OQL’s handling of joining multiple regions with indexes by preventing the LIMIT clause from being applied in intermediate execution steps.
GEODE-6808: Restored JSON backward compatibility.
GEODE-6851, GEM-2551: Prevented Pulse data browser from falsely showing that no data was found due to divison by zero.
GEODE-6904, GEM-2579: Fixed a problem in which members reconnecting after a network partition could start up without cluster configuration.
GEODE-6922, GEM-2550: Improved the retrieval of active sessions count by load-balancing the operations among multiple servers.
GEODE-6929, GEM-2590: Fixed an internal messaging problem that could cause customer logs to fill with spurious “Trying to reply twice to a message” errors.
GEODE-6823, GEM-2316: Fixed an issue during startup in which the initialization for
org.apache.geode.distributed.DistributedLockService mistakenly reports the member is closing,
causing initialization to hang.
GEODE-4958, GEM-2477: Changed logging when
encountered to now log as a “warn” statement rather than throwing the exception with a call stack.
GEODE-6527, GEM-2511: Fixed an issue in which a member that creates a partitioned region can result in “java.lang.IllegalStateException: Incompatible CacheLoader. CacheLoader is null in partitionedRegion Parent on another datastore” when the partitioned region had previously been altered in another member to change the cache writer or cache loader.
GEODE-6767, GEM-2511: Fixed an issue in which a partitioned region that is colocated with another partitioned region is altered to change entry time-to-live or idle-timeout while rebalancing, causing a loss of full bucket redundancy.
GEODE-6821, GEM-2548: Fixed an issue where the shared P2P message reader blocked when processing a message on a region with a serial sender.
GEODE-6746: Fixed an issue where the log message “Your SSL configuration disables hostname validation. ssl-endpoint-identification-enabled should be set to true when SSL is enabled” was repeatedly printed at the warning level. The message now prints only once as an info-level message.
GEODE-6724: Fixed a bug that prevented more than one cluster from being formed when more than one locator was concurrently created.
GEM-2514: Added the
geode-web JAR file to the
This list was updated on April 30, 2019.
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-2644: Provide ability to configure Geode appenders in log4j2.xml.
GEODE-3649: Added initialization of the PDX registry before attempting an auto-reconnect.
GEODE-5013, GEM-1964: Fixed a stack overflow issue with gfsh-initiated OQL queries and gets of JSON objects.
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-5959, GEM-2261: Fixed a performance issue related to execution of nested functions.
GEODE-6035, GEM-2272: Increased TCP/IP backlog defaults to enhance peer-to-peer connection formation.
GEODE-6064, GEM-2256: Protected SSL keystore password so it is no longer visible in plain text gfsh command results.
GEODE-6177, GEM-2324: Improved the gateway sender’s ability to re-authenticate upon reconnection following a dropped WAN connection.
GEODE-6205, GEM-2337: Modified the
create disk-store command to save the absolute path name rather than the relative one.
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-6244: Fixed a case in which a slowly responding member could mistakenly initiate disconnection of a better-responding member.
GEODE-6267, GEODE-6287, GEM-2352: Fixed server side memory leaks that occurred during client departure.
GEODE-6271, GEM-2356: Improved support of clients connected to multiple distributed systems by copying serialized types between clusters.
GEODE-6281, GEM-2344: Fixed a problem in which the utility that generates XML included entry values in the generated XML, causing Out of Memory errors during debugging operations.
GEODE-6304, GEM-2332: Improved the manner in which the Heap memory monitor tolerance counter is reset.
GEODE-6309, GEODE-6363: Modified the behavior of a restarting locator to try harder to find an existing cluster coordinator before assuming the role itself.
GEODE-6310, GEM-2334: Upgraded classpath version to control file descriptor consumption.
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-2213, GEM-2365: Fixed a source of spurious “socket read timeout” exceptions on client proxy reconnection requests by replacing existing proxies with new instances.
GEODE-6369: Terminated auto-reconnect attempts if reconnect is not possible.
GEODE-6389, GEM-2408: Improved propagation of entries to remote sites by disabling sharing of buffers in certain handshake contexts. (This change was reverted in v9.8.3.)
GEODE-6391, GEM-2386: Provided an event ID for the destroy region operation to avoid it being overlooked.
GEODE-6423, GEM-2410: Modified availability check following a network outage to honor 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.
GEODE-6522, GEM-2411: Fixed an issue with distributed system membership during shutdown operations that could cause a server to hang.
GEODE-6544, GEM-4883: Allowed retry of Pulse login following an unsuccessful login attempt.
GEODE-6559, GEM-2449: Modified auto-reconnect so it no longer loads outdated classes from cached JARs.
GEM-2261: Fixed a problem in which nested function calls resulted in a blocked thread.
GEM-2265: Modified multi-user security to use Pool APIs.
GEM-2271: Fixed a problem with portfolioIdIndex that led to the error “This method should not have been invoked.”
GEM-2299: Addressed slower performance of queries after v8 to v9 upgrade.
GEM-2367: Fixed an issue with a CPU surge during auto-reconnect on an under-provisioned system.
GEM-2396, GEM-2432, GEM-2436: Fixed reconnection issues following member shutdown.
GEM-2439: Fixed a problem encountered when using the REST API to invoke a parameterless function call.
GEM-2483: Fixed a problem in which locators consumed increasing amounts of memory over time.
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.
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.