Comment 4 for bug 665452

Revision history for this message
Jürgen Herrmann (xlhost) wrote :

I also get this this error from time to time with zodb 3.10.1, last time it happend about 30min. ago while packing my biggest relstorage db. First there was a conflict error:
Traceback (innermost last):
  Module Zope2.App.startup, line 197, in __call__
  Module ZPublisher.Publish, line 134, in publish
  Module Zope2.App.startup, line 301, in commit
  Module transaction._manager, line 95, in commit
  Module transaction._transaction, line 329, in commit
  Module transaction._transaction, line 446, in _commitResources
  Module ZODB.Connection, line 780, in tpc_vote
  Module relstorage.storage, line 788, in tpc_vote
--
ConflictError: database conflict error (oid 0x01, class BTrees.IIBTree.IITreeSet, serial this txn started with 0x00 1900-01-01 00:00:00.000000, serial currently committed 0x038bcd4602a83ccc 2011-01-24 01:42:00.622776)

Obviously this could not be resolved through retrying and any attempt to commit changes involving oid 0x01 throws that conflict error.

A few seconds later the "same oid" exceptions pop up:

Traceback (innermost last):
  Module ZPublisher.Publish, line 134, in publish
  Module Zope2.App.startup, line 301, in commit
  Module transaction._manager, line 95, in commit
  Module transaction._transaction, line 329, in commit
  Module transaction._transaction, line 443, in _commitResources
  Module ZODB.Connection, line 565, in commit
  Module ZODB.Connection, line 621, in _commit
  Module ZODB.Connection, line 687, in _store_objects
ValueError: A different object already has the same oid

Both errors go away on zope restart.