Bug 44219

GemStone/S 64 Bit

3.2,,,,,, 3.1


listInstances and other mulithreaded scan operations may hang on out-of-memory

If one of the threads that implements the multithreaded scan code runs
out of memory, this may not be handled correctly, causing the scan operation
to hang. This particularly may affect operations such as listInstances,
which can return a large result set that places large demands on temporary
object memory.


You may increase temporary object memory to avoid low memory conditions.
Using the variants that write to hidden sets, such as listInstancesToHiddenSet,
will avoid this issue, since object memory is not required for hidden sets.

Last updated: 5/22/14