GemStone/S 64 Bitâ„¢ 3.7.4.3 is a new release of the GemStone/S 64 Bit object server, fixing several critical bugs and with other minor changes and fixes.
These Release Notes include changes between the previous version of GemStone/S 64 Bit, v3.7.4.1, and 3.7.4.3; v3.7.4.2 was a limited distribution version. These Release Notes include all changes in 3.7.4.2 as well as 3.7.4.3. If you are upgrading from a version prior to 3.7.4.1, review the release notes for each intermediate release to see the full set of changes.
The Installation Guide has not been updated for this release. For installation, upgrade and conversion instructions, use the Installation Guide for version 3.7.2.
GemStone/S 64 Bit version 3.7.4.3 is supported on the following platforms:
For more information and detailed requirements for each supported platforms, please refer to the GemStone/S 64 Bit v3.7.2 Installation Guide for that platform.
The following versions of GBS are supported with GemStone/S 64 Bit version 3.7.4.3:
The GemStone/S 64 Bit v3.7.4.3 distribution includes VSD version 5.6.1. This is the same version of VSD that was included with the previous release, v3.7.4.1.
VSD 5.6.1 is included with the GemStone distribution, and can also be downloaded as a separate product from https://gemtalksystems.com/vsd/
If the SymbolGem is committing new symbols concurrently with a user login for an application userProfile that has certain password security features enabled, other Gems may commit references to oops that were provided by the SymbolGem for new symbols, but which the SymbolGem failed to commit. These oops may end up not existing, or being reused for unrelated objects. (#51494)
There are cases in which an out of memory (OOM) error can occur when configured memory should be able to grow. (#51486)
When upgrading from v3.6 or earlier, a GsObjectSecurityPolicy may have a nil objectSecurityPolicy. This caused upgrade to 3.7.4.x to fail. (#51463)
When there is a large amount of reclaim work and a commit record backlog, the ReclaimGem may still cause excessive repository growth. While the ReclaimGem considers low FreePages as of 3.7.4/3.7.4.1, this value was not updated quickly enough. The ReclaimGem also has tweaks in transaction state and handling checkpoints.
The following methods have been added to report Gem memory information:
System class >> _memoryFootprintMax
System class >> _memoryFootprintPercentUsed
System class >> _memoryFootprintUsed
In v3.7.4/3.7.4.1, GemStone included support for configurable keepalive on all sockets. The changes were incomplete; further fixes have been made in v3.7.4.2. (#51304)