[Zope] PANIC(300) after ZCatalog Find

[Chris McDonough]

Apparent Zope crash while trying "Find Items to ZCatalog" on a Zope 2.0.0
system with custom ZClasses on top of Linux 2.2.5 with a 19MB Data.fs.
This was the console output:

1999-09-21T22:47:57 INFO(0) Z2 CONFLICT Competing writes at,
/Catalog/manage_cat
alogFoundItems
------
1999-09-21T22:48:05 INFO(0) Z2 CONFLICT Competing writes at,
/Catalog/manage_cat
alogFoundItems
------
1999-09-21T22:48:16 INFO(0) Z2 CONFLICT Competing writes at,
/Catalog/manage_cat
alogFoundItems
------
1999-09-21T22:48:23 INFO(0) Z2 CONFLICT Competing writes at,
/Catalog/manage_cat
alogFoundItems
------
1999-09-21T22:48:32 INFO(0) Z2 CONFLICT Competing writes at,
/Catalog/manage_cat
alogFoundItems
------
1999-09-21T22:48:42 INFO(0) Z2 CONFLICT Competing writes at,
/Catalog/manage_cat
alogFoundItems
------
1999-09-21T23:05:38 PANIC(300) ZODB An storage error occurred in the last
phase 
of a two-phase commit.  This shouldn't happen. The application may be in a
hosed
 state, so we will not allow transactions to commit from here on

The symptoms were that the system shot up to 100% CPU utilization (one
Python process hogging the CPU) for about 20 minutes, then shot back down to
idle.  Even after idling out, no connections could be established with the
server.  I had to manually stop Zope and start it again to make it "go"
again.

You want that I try to replicate it?

- C