1. GemStone/S 64 Bit 3.3.3 Release Notes

Platforms for Version 3.3.3

GemStone/S 64 Bit version 3.3.3 is supported on the following platforms:

• Solaris 10 and 11 on SPARC
• Solaris 10 on x86
• AIX 6.1 on POWER6 and POWER7 and
  AIX 7.1 on POWER7 and POWER8
• Red Hat Enterprise Linux Server 6.4, 6.5, 6.7, and 7.1;
  Ubuntu 12.04 and 14.04; and SUSE Linux Enterprise 12, all on x86
• OS X 10.9.5 (Mavericks), with Darwin 13.4.0 kernel, on x86

Supported Windows client platforms are

• Windows 7, Windows 2008 R2, Windows 8, and Windows 10

For more information and detailed requirements for each supported platforms, please refer to the GemStone/S 64 Bit v3.3.1 Installation Guide for that platform.

GemBuilder for Smalltalk (GBS) Versions

GemStone/S 64 Bit version 3.3.3 requires GBS version 8.1 or later for VisualWorks Smalltalk, or version 5.4.3 or later for VA Smalltalk. The following versions of GBS are certified with GemStone/S 64 Bit version 3.3.3:

VSD Version

The GemStone/S 64 Bit v3.3.3 distribution includes VSD version 5.3. The previous version of GemStone/S 64 Bit, v3.3.1, included VSD v5.2.

VSD v5.3 includes a number of new features, including control over saving display preferences and secondary sort keys.

For more information, see the Release Notes for VSD v5.3, or the VSD home page.

GsNMethod recompile could not resolve non-class literals

Change in 3.3.3; not fixed in 3.3.2

Upgrade to v3.3.x requires method recompile, which can be done either by filein or sending recompileAllMethods to the class. The recompile failed if the method included non-class literals. (#46519)

Remote page server log not deleted on stone shutdown

Change in 3.3.3; not fixed in 3.3.2

Remote page servers create a runpgsvrmain* log in a directory that is by default the users’s home directory. This log was not deleted on clean exit. (#46535).

Updated SSL libraries

The version of OpenSSL has been updated to 1.0.2j.

Changes in listening on hostname for Ubuntu

Ubuntu by default creates entries for 127.0.1.1 for hostname. Listening on "any interface" or on localhost did not pick up connects to 127.0.1.1, and so these listens would not detect connects using the hostname. Now, the Stone and NetLDI will also listen on the hostname port when that is not the same as localhost. (#46452)

Incorrect tranlog entries for insert into a large byte object

When a large object is modified, changes to leaf objects composing it must be tranlogged. In the case of byte objects (such as Strings), insert operations did not correctly log the changes, so after restore the state could be inconsistent. (#46474)

Gem log handling in case of disconnect during login

During the login process, after the gem log is created but before the login completes, if the client exits then the Gem sees this as an error. However, since the client may have elected to exit, this may not actually be an error, so for this case, the exit was done cleanly and the log deleted. However, fatal client errors during login also were handled this way, so log file handling has been changed. (#46419)

Now, while the Gem still exits cleanly, the Gem log file is not deleted.

Excessive root page reads during remote login

When a remote Gem logs in, and there is not already a page server for that remote node on the Stone’s host, the page server that is started on the Stone’s host reads the root pages for each extent. The page servers read each root page several times, which impacted performance when there was a large number of extents. (#46476)

Stone frozen after random data sent to listening port

When random data is sent to GemStone listening ports, it could have resulted in the Stone freezing. (#46477)

DateTime asStringISO8601 reported time/timezone incorrectly

The method DateTime >> asStringISO8601 should report the time as adjusted for the DateTime’s timezone, followed by the timezone offset. Instead, it was reporting the time in local time, but including the timezone offset for the timezone. This produced incorrect results when executed for DateTimes that were not in the current timezone. (#46315)

Issues involving gslist

GsNMethod instance variables not protected

Some instance variables are unsafe to access directly due to the way they are stored in memory. These accesses are protected; however, instVarAt: was not reimplemented to provide safe access. This method has been added to GsNMethod. (#46405)

Connecting on secure socket may hang rather than timeout

GsSecureSocket >> secureConnect and secureAccept may have waited forever if the connection did not complete, rather than timing out. (#46375)

AES Encryption issues

listReferences could have missed first dynamic instance variable key

Due to an off-by-one error, the first dynamic instance variable’s key was not included when performing scans for listReferences methods. (#46400)

changeClassTo: disallowed for NSCs with fewer named instance variables

When changeClassTo: is requested, and the number of named instance variables is fewer than that of the original class, the values in the removed named instance variable slots may be moved to unnamed instance variables. This caused object corruption for instances of IdentityBag, and data corruption for instances of IdentitySet. (#46475 )

Object >> storeOn: failed for large strings

The method Object >> storeOn: had a typo that was exposed for large strings. (#46381)

Debugger issues

Improved reporting of method needs recompile error after upgrade

After upgrade from an earlier version with method version differences, code must be recompiled before it can be executed. Attempting to execute a method that was not recompiled previously, returned an error message of the form " GsNMethod with oop 33230593 needs recompile", which was unhelpful without further analysis. Now, the error include the class and selector of the method that was not recompiled, as well as its OOP. (#46000)

_tempObjSpaceMax can return negative values on large TOC

When GEM_TEMPOBJ_CACHE_SIZE was configured to larger than about 2800000, the method System >> _tempObjSpaceMax returned a negative value. (#46384)

Unclear compiler error when assigning to an argument

When method code attempts to assign to an argument variable, which is illegal, the message was "expected a variable". This has been clarified, and now says "Expected an assignable variable". (#46455)

GsSysLog write handling of non-string input

Previously, writing non-string data to GsSysLog did not error, but did not do a write. (#45999)

ProfMonitorTree object creation report not generated

Due to changes in underlying profiling data in v3.3, the tree version of the object creation report did not find any data, and no results were reported. (#45441)

Subclassing GsExternalSession

Code that prevented practical subclassing of GsExternalSession has been cleaned up. (#46396)