LATEST VERSION: 8.0.0 - CHANGELOG
Pivotal GemFire® v8.0

Pivotal GemFire Native Client 8.0.0 Release Notes

Pivotal GemFire Native Client 8.0.0 Release Notes

Release Date 12 August 2014
Last Document Update 12 August 2014
Additional Documentation All GemFire 8.0.0 Documentation

What's in the Release Notes

The release notes cover the following topics:

What's New in Pivotal GemFire Native Client 8.0.0

Pivotal GemFire Native Client 8.0.0 includes the following updates and new features:

  • Automatic PDX Serialization for C++
  • Various bug fixes. See Resolved Issues.

PDX Autoserialization for C++ Native Client Applications

You can allow your native client C++ applications to automatically PDX serialize and deserialize domain objects without having to add any extra code by using the pdxautoserializer command line tool provided with the native client.

When using the native client C++ API, you can automatically serialize and deserialize domain objects without making any code changes to those objects or having to implement a PdxSerializer or PdxSerializable interface and their related fromData and toData methods. The GemFire native client includes a command-line utility, pdxautoserializer, that allows you to generate C++ code that will serialize your domain objects in the PDX format for you.

See Using Automatic PDX Serialization for more details.

Installing Pivotal GemFire Native Client 8.0.0

You can download Pivotal GemFire Native Client 8.0.0 (and Pivotal GemFire 8.0.0) from the Pivotal GemFire product download page.

Pivotal GemFire Native Client 8.0.0 installers are available in ZIP (Linux, Solaris) and MSI (Windows) format.

For details on how to install Pivotal GemFire Native Client 8.0.0, see Installing the Native Client in the Pivotal GemFire Native Client User's Guide

Resolved Issues

The following issues have been resolved in Pivotal GemFire Native Client 8.0.0:

  • #915. SIGSEGV in PDX PreservedDataExpiryHandler. This issue has been fixed.
  • #930. Transaction commit fails when server persistent transaction is enabled. This issue has been fixed.

Known Issues

The following key issues with Pivotal GemFire Native Client 8.0.0 have been registered as bugs in the Pivotal bug tracking system:

ID Title Description Workaround
430 Difference in ClassID type/range between .NET, C++ and Java The difference in the ClassId type/range between C++, .NET and Java could clash and cause undefined behavior. Use class IDs well within the signed integer range to avoid undefined behaviour between C++, .NET and Java APIs.
469 Exceptions from the server containing non-ASCII data are not correctly logged by the client The Native Client is interpreting the Exception strings that are sent from the server as ASCII; however, when the server is configured for a non-English locale that has a message bundle (such as "ja_JP" aka Japanese) it is possible for these strings to contain utf-16 encoded data. In these cases the Native Client will split each 2-byte character into two 1-byte characters which produces gibberish. The problem only impacts logging, all non-ASCII strings stored in the cache itself are correctly preserved. n/a
584 Region expiration does not work when statistics are disabled If statistics sampling is disabled, then region expiration functionality does not work. Enable statistics