Bug 46290

GemStone/S 64 Bit

3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.2, 3.3.1, 3.3, 3.2.17, 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.x, 3.2

3.4

Idle gems in transactionless mode could be terminated by sigAbort

If a transactionless session is executing bytecodes, it will respond to sigAbort by silently aborting and continue execution.

However, if the session is entirely idle, the session will not notice the sigAbort or sigLostOT, from the Stone, and may be killed by the Stone as part of lostOT handling


Last updated: 8/1/18