GemStone/S 64 Bitâ„¢ 3.6.8 is a new version of the GemStone/S 64 Bit object server. Version 3.6.8 fixes a critical bug in v3.6.7, and includes other changes and bug fixes. We recommend all customers that are not currently able to upgrade to v3.7.x, upgrade to this new version.
These Release Notes include changes between the previous version of GemStone/S 64 Bit, v3.6.7, and v3.6.8. If you are upgrading from a version prior to 3.6.7, 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.6.7.
GemStone/S 64 Bit version 3.6.8 is supported on the following platforms:
For more information and detailed requirements for each supported platforms, please refer to the GemStone/S 64 Bit Installation Guide for that platform.
The following versions of GBS are supported with GemStone/S 64 Bit version 3.6.8:
The GemStone/S 64 Bit v3.6.8 distribution includes VSD version 5.6.1. This is the same version that was included with the previous GemStone/S 64 Bit version, v3.6.7. VSD 5.6.1 includes a fix for a rare but significant bug.
VSD v5.6.1 is included with the GemStone distribution, and can also be downloaded as a separate product. For details or to download, go to https://gemtalksystems.com/vsd/.
set autostacksave requires one argument, OFF or ON.
If on, STACK SAVE is executed automatically for each error returned to topaz from an execution (doit, send, or run).
The default is ON if the topaz stdin is a terminal, otherwise default is OFF.
In code changes introduced in v3.6.7, there was a corner case in which an iteration in creating the transitive closure of live objects could terminate before it was complete, such that some objects could be omitted. These objects would be subject to garbage collection. This is expected to be rare and related to configurations with multiple extents with many threads. (#50847)
Due to this bug, version 3.6.7 should not be used, and is not available for download.
After an unclean Stone shutdown, such as a kill -9, on restart the Stone performs recovery by reading the current tranlog that was being written before the shutdown. When tranlogs are configured as a list of raw partitions, there is a codepath in which the stone may fail to find the tranlogs needed for recovery; in this case, the stone will not start unless startstone -N is used. (#50843)