GemStone/S 64 Bitâ„¢ 3.5.5 is a new version of the GemStone/S 64 Bit object server, including several critical bug fixes. We recommend everyone using or planning to use GemStone/S 64 Bit upgrade to this new version.
These release notes describe changes between the previous version of GemStone/S 64 Bit, version 3.5.4, and version 3.5.5. If you are upgrading from a version prior to 3.5.4, 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.5.3.
GemStone/S 64 Bit version 3.5.5 is supported on the following platforms:
For more information, please refer to the GemStone/S 64 Bit Installation Guide for v3.5.3 (the most recent version of the Installation Guides) for that platform.
GemStone/S 64 Bit version 3.5.5 requires GBS version 8.4 or later for VisualWorks Smalltalk, or version 5.4.5 or later for VA Smalltalk.
The following versions of GBS are supported with GemStone/S 64 Bit version 3.5.5.
Windows 7 reached end of life in January of 2020. While GemTalk continues to test on and support GemStone clients on Windows 7, it is no longer considered fully certified.
For more details on supported GBS and client Smalltalk platforms and requirements, see the GemBuilder for Smalltalk Installation Guide for that version of GBS.
The GemStone/S 64 Bit v3.5.5 distribution includes VSD version 5.5.1. The previous version of GemStone/S 64 Bit, v3.5.4, included VSD v5.5.
VSD version 5.5.1 includes a number of new features and bug fixes. For details on the changes, see the Release Notes for VSD v5.5.1.
VSD 5.5.1 is included with the GemStone distribution, and can also be downloaded as a separate product from https://gemtalksystems.com/vsd/
Gemstone/S 64 Bit v3.5.5 is distributed with libraries compatible with GemConnect v2.4. Previous versions of GemStone/S 64 Bit included GemConnect v2.3-compatible libraries. If you are using GemConnect v2.3 and require libraries compatible with 3.5.5, or if you need libraries for another configuration, contact GemTalk Technical Support.
When connecting a GsTsExternalSession to a repository running a different version of GS64, the method GciTsLibrary >> version: tests that the other version is compatible. The initial implementation was not flexible regarding the input argument.
If the initial use of send:to:withArguments: for a particular instance of GsTsExternalSession has fewer arguments than a later use of the same method, the later use may get an error such as "offset not within bounds of memory owned by aCByteArray". (#49284)
When a login fails with error 4138/REP_ERR_SYSTEM_REP_NOT_ATTACHED, it did not report the details of why the login failed. The reported case was an extent file permissions issue. (#49273)
When System _writtenObjects is executed within a nested transaction, it does not return the full closure of the transaction. This usage should be replaced with System enumerateDirtyList: -1 .
Rare cases have been seen of UncontinuableErrors in GemConnect, related to scheduler interrupts for asynchronous exceptions. These may also occur during non-GemConnect execution of GCI code.
GCI_PERFORM_FLAG_DISABLE_ASYNC_EVENTS is a flag passed to GciExecute* and GciPerform*, which prevents asynchronous exceptions such as InterSessionSignal and TransactionBacklog from being signalled during the execution. This flag now also disables scheduler interrupts caused by an expiring higher priority Delay. (#48818)
Linked topaz sessions and HostAgents may have excessive CHeap memory use after failed X509 logins. (#49230)
If the file to which statmonitor is writing is deleted, statmonitor opens a new file and continues writing. However it may write the buffered data to the new file before it writes the statmonitor header; which means VSD cannot read the file. (#49233)
When running with statmonitor -r or -R, which automatically create new files periodically, a new filename is generated containing an incremented sequence number. However, if the current file is moved or deleted, a file with that same sequence number was generated, rather than the next in the logical sequence. (#49235)
GsObjectInventory >> profileObjectsInBm:
GsObjectInventory >> profileObjectsInFile:
These methods were unnecessarily added in v3.5.3.
GsBitmap >> peakLast
Duplicate of the existing method GsBitmap >> peekLast.
Object >> _idxForCompareEqualToDoubleByteSymbol:collator:
Object >> _idxForCompareEqualToQuadByteSymbol:collator:
Object >> _idxForCompareEqualToSymbol:collator: