Known Issues in GemFire Native Client 3.6.3

Last updated: 06/13/2012

Ticket Created Title Description Workaround
#90 10/13/06 Gathering Statistics may fail on some Windows platforms with an error code indicating that permission denied. Users may be required to have Administrator rights or Performance Monitor Users group rights on some Windows platforms in order to read the registry performance counters (on which the GemFire Native Client's statistics sampling is based.) Disable statistics sampling or grant Administrator rights or Performance Monitor Users group rights to the user running the process on the local machine.
#316 11/12/08 Running Native Client applications from within the Microsoft Visual Studio Debugger may cause performance degradation When running C# application with our native client, sometimes a significant (about a 10x) performance degradation is observed in de-serialization when running inside the Visual Studio environment. This is caused by the Visual Studio memory manager when it copies data back and forth between managed and unmanaged code spaces. Confirm the performance of your application outside of Visual Studio to eliminate the debugger's memory management overhead as a factor.
#430 04/24/09 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 09/02/09 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.
#513 02/09/10 CacheableString.Value may cause AccessViolationException during memory pressure In some scenarios such as low memory situations CacheableString.Value may throw an AccessViolationException. Use an intermediate temporary value such as: CacheableString temp = ((CacheableString)region.Get(key)); var y = temp.Value; And use "y" from then on.
#584 05/28/10 Region expiration does not work when statistics are disabled. If statistics sampling is disabled then region expiration functionality does not work.
#634 02/01/11 Bulk operation (GetAll) does not refresh PR single hop metadata. Bulk operation GetAll does not refresh PR single hop metadata if it is the only operation performed. The client metadata may always remain stale affecting single hop performance.
#639 02/22/11 Destroy on a non existent entry reduces region size by one. If a destroy operation is performed on a non existent entry in a region the region size reported is reduced by one.
#768 06/08/12 On Windows, the GemFire native client installer does not reset the GFCPP variable if it is already set If the GFCPP variable is already set in Windows, the native client installer does not reset the value of the variable. After upgrading the native client on Windows, manually redefine the GFCPP variable to point to the new native client installation. Alternatively, you can copy the NCProduct\bin folder to the application\bin folder to run native client without setting the GFCPP variable.