Server out of memory due to GBS references
GemStone/S 64 Bit, unlike GemStone/S, has risk of out of memory
error if the demand for temporary object memory exceeds the
configured size. If an exported object is retaining references
to many server objects in temporary memory, the exported object
may not get reported back to the server as unexported quickly
enough to prevent temporary memory object growth. Unexported object
ids are flushed to the server after 2000 objects are unexported.
If a small number of very large objects exported to the client
consume large amounts of temporary object space, in GemStone64 bit
servers, there could be an out of memory condition.
Workaround
Before temporary object space on the server gets too full,
create 2000 very small, non-special server objects, replicate them
to the client, and release them. This will force any unexported
objects on the client to be flushed to the server.
Last updated: 9/10/07