ConflictError: database conflict error (oid 0x0b01, class Products.zms.zmstrashc

"saleyka" <[email protected]>
Newsgroups gmane.comp.cms.zms.devel
Message-ID <[email protected]>
Hi,

my Zope slows down it's performance immediately after startup. After a
few clicks it's not responding anymore. I switched to debug mode and
found the following errror message in the event.log file:
-------
2007-10-25T11:59:07 BLATHER Conflict traceback 
Traceback (most recent call last):
  File
"C:\Programme\Zope-2.8.4-final\lib\python\ZPublisher\Publish.py", line
119, in publish
    transactions_manager.commit()
  File
"C:\Programme\Zope-2.8.4-final\lib\python\Zope2\App\startup.py", line
215, in commit
    transaction.commit()
  File
"C:\Programme\Zope-2.8.4-final\lib\python\transaction\_manager.py",
line 84, in commit
    self.get().commit(sub)
  File
"C:\Programme\Zope-2.8.4-final\lib\python\transaction\_transaction.py",
line 381, in commit
    self._saveCommitishError() # This raises!
  File
"C:\Programme\Zope-2.8.4-final\lib\python\transaction\_transaction.py",
line 379, in commit
    self._commitResources()
  File
"C:\Programme\Zope-2.8.4-final\lib\python\transaction\_transaction.py",
line 424, in _commitResources
    rm.commit(self)
  File "C:\Programme\Zope-2.8.4-final\lib\python\ZODB\Connection.py",
line 462, in commit
    self._commit(transaction)
  File "C:\Programme\Zope-2.8.4-final\lib\python\ZODB\Connection.py",
line 495, in _commit
    raise ConflictError(object=obj)
ConflictError: database conflict error (oid 0x0b01, class
Products.zms.zmstrashcan.ZMSTrashcan)
------
What can I do?

Cheers

Joachim 

My system:
ZMS: ZMS 2.8.1-a19  (Build #122f)
ZOPE: (Zope 2.8.4-final, python 2.3.5, win32)
PYTHON: 2.3.5 (#62, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)]
System Platform: win32
System Time: 2007/10/25 10:46:11.593 GMT+2
Running For: 9 min 7 sec
ZODB Location: C:\portal/var/Data.fs
Database Size: 70.5M
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.