Pivotal GemFire Native Client 9.2 Release Notes

What’s New in Pivotal GemFire Native Client 9.2.4

The Pivotal GemFire Native Client 9.2.4 includes the following new feature:

  • A fix for issue GEMNC-459, described below, introduces new behavior affecting applications that use SSL encryption. A new property, ssl-strict-mode, has been introduced to force the verification of the cluster. See Issues Resolved in Verson 9.2.4, below, for details on when and how to apply this new property.

What’s New in Pivotal GemFire Native Client 9.2.0

The Pivotal GemFire Native Client 9.2.0 included the following new feature:

  • A new library, Pivotal.GemFire.Session, that implements Microsoft’s SessionStateStoreProviderBase SPI.

Installing the GemFire Native Client 9.2

Download the Pivotal GemFire Native Client 9.2 from the Pivotal GemFire product download page. There is a ZIP format file for all platforms. See Installing the Native Client for installation instructions.

Native Client version 9.2 works with Pivotal GemFire versions 9.0.0 and later. Upgrade all servers running Pivotal GemFire to version 9.0.0 or a later version.

Issues Resolved in Pivotal GemFire Native Client

The following issues, listed by their release numbers, have been resolved in version 9.2 of the Pivotal GemFire Native Client.

9.2.4

  • GEMNC-459: When SSL is enabled (ssl-enabled=true), a client should require a truststore containing a valid SSL certificate. Testing revealed that the Native Client library, to date, has not been enforcing this requirement. Beginning with Native Client version 9.2.4, when SSL is enabled the developer must provide a truststore that (a) exists, and (b) is a real SSL certificate.

    In order to avoid breaking legacy applications, version 9.x native clients will not, by default, enforce that the cluster’s credentials match the truststore certificate, only that the truststore certificate is valid.

    A new property, ssl-strict-mode, has been introduced to force the verification of the cluster. This is the correct and expected behavior for SSL mode, and developers who want SSL to behave as intended should set the ssl-strict-mode parameter to true.

9.2.3

  • GEODE-6835, GEMNC-442 Fixed an authentication exception (“AuthenticationRequiredException: No security credentials are provided”) that could result in a dropped server connection.

9.2.2

  • GEODE-6624: Improved reporting of a serialization error that previously was obscured by a crash due to nested exceptions.

  • GEMNC-436: Closed a memory leak that occurred in C++ native client memory increasing over time when running a query multiple times.

9.2.1

  • GEMNC-420: Fixed a memory leak that occurs when running frequent queries.