Known Issues in vFabric GemFire Native Client 7.0.0
Last updated: 10/25/2012
| Id | Created | Title | Description | Workaround | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| #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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #834 | 10/22/12 | removeEx(key) returns true even when entry is not present (non existent entry) in the region. | removeEx(key) returns true even when entry is not present (non existent entry) in the distributed region. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||