Bug 44903

GemStone/S 64 Bit

3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2

All Platforms

System class >> standbyVmSessionId removed

The method System class >> standbyVmSessionId was intended to be deprecated, but was removed from the product.  In addition, the non-functional methods   startStandbySession and stopStandbySession were also removed.

Note that while the Smalltalk methods were removed, the underlying zero argument primitives called by them are still present.  Customers are cautioned *not* to attempt to restore these commands by directly calling _zeroArgPrim: with either arguments 149 or 15 0.  It is still safe to call primitive 151 directly to retrieve the standby session ID.

Workaround

Use OS level shell scripts to execute appropriate startlogsender / startlogreceiver commands.

If you need to retrieve the session ID of the standby session, you can execute:

System _zeroArgPrim: 151

or alternatively, restore the method standbyVmSessionId by logging in as SystemUser and entering/committing the following code:

classmethod: System
standbyVmSessionId

"Return the session ID of the logsender or logreceiver session
 associated with this stone's role in a hotstandby pair."

^ self _zeroArgPrim: 151

%


Last updated: 1/23/15