Bug 44337

GemStone/S 64 Bit

3.2.1, 3.2, 3.1.0.6, 3.1.0.5, 3.1.0.4, 3.1.0.3, 3.1.0.2, 3.1.0.1, 3.1

3.2.2

DataCurator and SystemUser sessions not forcibly terminated by stopSession:

A session is logged in as SystemUser or DataCurator, when sent a stopSession: or terminateSession:timeout: message, gets a stop signal and will logout at next stone interaction. However, no further action is taken by Stone to forcibly logout or send SIGTERM to that session, as is done with sessions logged in as non-system userIds.


Last updated: 7/28/14