Dieter, Your lucid description of the source of the "AttributeError: Surrogate instance has no attribute '_p_oid'" error in the mailing list archives explains what's happening, but I am at a loss to identify the method that registers the surrogate and does not have an _p_oid instance. My problem is trying to identify the source of the failure. There are a couple of external procedures used in the QLOG method which caused the conflict error, but nothing other than vanilla DTML nearby in the log. Do you have any suggestions for localizing the problem? This is all running on Zope 2.6.2b3, Python 2.3.1, RH7.3. -------------------------------------------------------------------
From the error log:
2004-01-13T17:15:21 ERROR(200) ZODB A storage error occured during transaction abort. This shouldn't happen. Traceback (innermost last): File /home/zopesys/lib/python/ZODB/Transaction.py, line 262, in commit File /home/zopesys/lib/python/ZODB/Transaction.py, line 393, in _commit_error AttributeError: Surrogate instance has no attribute '_p_oid' ------ 2004-01-13T17:15:21 INFO(0) ZODB conflict error at /lms/QLOG (2 conflicts since startup at 2004-01-13T12:24:00) ------ 2004-01-13T17:29:07 INFO(0) Z2 Caught signal SIGTERM ------ 2004-01-13T17:29:07 INFO(0) Z2 Closing all open ZODB databases ------