GigaSpaces 6.0.3 Fixed Issues

                                               
Summary: Fixed issues in GigaSpaces 6.0.3 (build 2040)

Overview

This list includes fixed issues since GigaSpaces 6.0.2.

The Linux 32 bit C++ package provided with the installation is not functional. A functional version is available through GigaSpaces Support.

Upgrading GigaSpaces 6.0.2 to GigaSpaces 6.03? See this migration document.

  • GS-3546 – Fixed: Split brain log messages are now SEVERE.
  • GS-1482 – Fixed: The partition id is not set when using central data base configuration.
  • GS-3587 – Fixed: DetailedUnusableEntryException might be thrown when calling parallel read on local cache.
    Support case ID: 3519
  • GS-3694 – Fixed: DataIterator objects that are created by the data source when reading data from the space are not closed by the space resulting full consumption of the database connection pool that leads to space hang or OutOfMemoryException.
  • GS-3566 – Fixed: In a LRU with Primary Backup configuration, OutOfMemoryException is thrown on the backup even when the Memory Manager is turned on.
    Support case ID: 3464
  • GS-3461 – Fixed: Command not found error is shown when running gs.sh and setting Xbootclasspath.
    Support case ID: 3306, 3466
  • GS-3448 – Fixed: NO_HTTP has no affect when starting GSM/GSC/LH (Webster is always started).
    Support case ID: 3452
  • GS-3449 – Fixed: Webster allows use of ""../"" in the URL, resulting in the ability to get files outside the root folders.
    Support case ID: 3452
  • GS-3590 – Fixed: GSM failover causes relocation of Processing Units to fail.
  • GS-3612 – Fixed: Default network detection timeout and amount of retries are hard coded.
    Support case ID: 3500
  • GS-3797 – Fixed: DiskMonitor (in the Service Grid) might not close file descriptors when executing "df -k" (might cause out of file descriptors OS error).
    Support case ID: 3492
  • GS-3620 – Fixed: When using a read-only external data source, performing read after take returns no result.
    Support case ID: 3574
  • GS-3169 – Fixed: Incompatible Class Change Error thrown during normal write operation, even though no change was made to the class.

Labels

 
(None)