Bug 27201

GemStone/S

6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.1.5, 6.1.x, 6.0.x, 5.1.5.1, 5.1.5, 5.1.4

Windows

On Windows, topaz -l doesn't clean up after forced termination

If a linked topaz session is forcibly terminated, either by another session
or by doing System>>shutDown, it will fail to properly release its
shared memory resources. This can prevent stone startup or future
logins from that invocation of topaz.

Workaround

Exit topaz after a session has been terminated.


Last updated: 7/11/11