Bug 43108


GemStone/S 64 Bit,, 3.1, 3.0.1, 3.0


markForCollection may hang

There is a timing condition that can cause the markForCollection to hang,
as the commit record backlog approaches the StnSignalAbortCrBacklog limit.

This bug can be diagnosed in statmonitor data, by SessionStat03 flatlining
on 5 and ProgressCount freezing.


The chances of hitting this bug are timing-dependent as well as depending
on a commit record backlog. Increasing the STN_SIGNAL_ABORT_CR_BACKLOG
(#StnSignalAbortCrBacklog) before starting the markFocCollection will reduce
the likehood of hitting this bug.

Last updated: 5/15/13