Bug 39842

GemStone/S

6.3.1, 6.3, 6.2.1, 6.2

All

6.5

sigAborts handled during GsFile open/close can result in errors

If a sigAbort handler handles a sigAbort while a GsFile is being
opened and closed, session state can be lost, resulting in an
error #rtErrLostSessionState.

Workaround

The problem is related to the way signals are used to implement
GsFile operations on client files.  Using server, rather than client
files (openWriteOnServer:, etc) avoids the problems.

Using linked sessions, rather than RPC sessions, also avoids the
problem.


Last updated: 4/9/09