Hi, I am new to this group, so please forgive me if this problem has been addressed in the past. I was not able to find any solution on Google or elsewhere. I am running Zope, MySQL and Plone and occasionally Zope will lockup under load. Below is the messages from the log: 2003-06-18T14: 06:31 ERROR(200) ZODB A storage error occurred during transaction abort.  This shouldn't happen. Traceback (innermost last):   File /xxx/2-6-1/lib/python/ZODB/Transaction.py, line 261, in commit   File /xxx/2-6-1/lib/python/ZODB/Transaction.py, line 392, in _commit_error AttributeError: Surrogate instance has no attribute '_p_oid' ------ 2003-06-18T14: 06:31 ERROR(200) SiteError http://xxx/mail_password Traceback (innermost last):   File /xxx/2-6-1/lib/python/ZPublisher/Publish.py, line 102, in publish   File /xxx/2-6-1/lib/python/Zope/App/startup.py, line 200, in commit   File /xxx/2-6-1/lib/python/ZODB/Transaction.py, line 261, in commit   File /xxx/2-6-1/lib/python/ZODB/Transaction.py, line 392, in _commit_error AttributeError: Surrogate instance has no attribute '_p_oid' It happens within any ZPT, not only mail_password.  After this occurs zope locks up within a minute or so. We have been getting this almost daily, and need to restart Zope when it happens. I found an unresolved issue in the zope collector ( http://collector.zope.org/Zope/852 ) which seems to be the same problem.   I have found several work arounds: 1) Apparently a work around is to run Zope 2-6-0 instead of 2-6-1 . 2) Setup the tables in MySQL to support transactions. Currently our MySQL tables are not enabled for transactions.   Does anyone else have experience with this issue? I have a rather large installation and am reluctant to roll back to 2-6-0 :( -- Craig Funk PanTechnica Corporation