GemStone/S 64 Bit 3.2.17 is a new version of the GemStone/S 64 Bit object server. This release include fixes for a number of serious bugs.
These release notes provide changes between the previous version of GemStone/S 64 Bit, version 3.2.16, and version 3.2.17. If you are upgrading from a version prior to 3.2.16, review the release notes for each intermediate release to see the full set of changes.
No specific Installation Guide is provided with this release. For details on installing GemStone/S 64 Bit 3.2.17 or upgrading from earlier versions of GemStone/S 64 Bit, see the GemStone/S 64 Bit Installation Guide for v3.2.6 for your platform.
GemStone/S 64 Bit version 3.2.17 is supported on the following platforms:
Note that Solaris on SPARC support is being deprecated and will be available for development only. Solaris on x86 will continue to be fully supported.
The following versions of GBS are supported with GemStone/S 64 Bit version 3.2.17.
The GemStone/S 64 Bit v3.2.17 distribution includes VSD version 5.3, the same version of VSD as v3.2.16. For details on VSD versions, see the documentation on the website at gemtalksystems.com/products/vsd/versions/.
If a Gem exits prematurely during the wrong point in the Gem-to-Stone login handshake, a counter in the Stone that was incremented did not get the appropriate decrement. This reduced the maximum possible sessions that could log in (from the limit set by STN_MAX_SESSIONS or license limits). (#46817)
Calling GsFile >> position: with a argument greater or equal to 231 (2147483648) returned nil, and caused subsequent calls to GsFile >> position to return incorrect values. (#46750)
If you do a store traversal of an IdentitySet, and the report is split across traversal buffers so that the first report in a buffer starts with one of the private named instvars that is not the first instvar, the server reports the error GbsObjErrOopNotAllocated. (#46822)
If the Stone’s send to a gem results in an EWOULDBLOCK, the Out of Band (OOB) bytes may have been lost. OOB processing supports sigAbort handling. (#46846).
When a machine is almost out of swap space, such that an mmap from reserved memory fails, there are cases where the Gem may crash. (#46848)
When a Gem dies due to a malloc failure, it forks a pstack to record the stack. This may hang if there is insufficient virtual memory. (#46830)