Bug 43656

GemStone/S 64 Bit

3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 3.1.0.6, 3.1.0.5, 3.1.0.4, 3.1.0.3, 3.1.0.2, 3.1.0.1, 3.1, 3.0.1, 3.0, 2.4.8, 2.4.7, 2.4.6, 2.4.5.1, 2.4.5, 2.4.4.7, 2.4.4.6, 2.4.4.5, 2.4.4.4, 2.4.4.3, 2.4.4.1, 2.4.4, 2.4.x

All Platforms

killing gem/topaz while doing index removal can crash reclaim GcGems

Killing a gem/topaz session while it is doing an index removal operation includes a possible risk of a reclaim GcGem crashing with a page cache fault.

Index removal operations include:
    #removeAllIndexes
    #removeEqualityIndexOn:
    #removeIdentityIndexOn:

The crashed reclaim GcGem logs will contain entries like:

*************** Page Cache Fault ***************
  occurred at /some-file-directory-structure/pagecache.hc: NN
  message is: Page header fault on page NN, expected kind 7, found kind NN

(Where NN indicates numbers)


Last updated: 5/6/14