Bug 49651

GemStone/S 64 Bit

3.6.5, 3.6.4, 3.6.3, 3.6.2, 3.6.1, 3.6, 3.5.8, 3.5.7, 3.5.6, 3.5.5, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5

Repository multithreaded-scans cannot complete if voting or atomic promote occurs during the scan

In versions 3.6.1 and earlier, when a multi-threaded span operation, such as listInstances and allReferences, detects that voting or atomic promote has occurred, the scan operation returns an empty collection, even if the scan operation should return resulting objects.

In version 3.6.2 and later, this circumstance will instead signal an error, with the message "Voting occurred or an atomic promote detected during the operation, results are compromised- please try again".

Workaround

Retrying the operation should work to return the scan results. You may limit exposure by not enabling epoch garbage collection, and by not starting a Respository multi-threaded scan operation during or shortly after a markForCollection.


Last updated: 9/8/22