Using .../manage and editing/storing the atttribute serial number doesn't lead to the conflict.
The traceback of the conflict: Traceback (most recent call last): File "/opt/zenoss/lib/python/Zope2/App/startup.py", line 167, in zpublisher_exception_hook v.reraise() File "/opt/zenoss/lib/python/ZPublisher/Publish.py", line 120, in publish transactions_manager.commit() File "/opt/zenoss/lib/python/Zope2/App/startup.py", line 233, in commit transaction.commit() File "/opt/zenoss/lib/python/transaction/_manager.py", line 84, in commit self.get().commit(sub) File "/opt/zenoss/lib/python/transaction/_transaction.py", line 381, in commit self._saveCommitishError() # This raises! File "/opt/zenoss/lib/python/transaction/_transaction.py", line 379, in commit self._commitResources() File "/opt/zenoss/lib/python/transaction/_transaction.py", line 427, in _commitResources rm.tpc_vote(self) File "/opt/zenoss/lib/python/ZODB/Connection.py", line 637, in tpc_vote s = vote(transaction) File "/opt/zenoss/lib/python/ZEO/ClientStorage.py", line 893, in tpc_vote return self._check_serials() File "/opt/zenoss/lib/python/Z EO/ClientStorage.py", line 877, in _check_serials raise s ConflictError: database conflict error (oid 0x2ca84d, class BTrees._IOBTree.IOBucket, serial this txn started with 0x037f4aad83073777 2009-07-12 17:17:30.709732, serial currently committed 0x037f4aad956c4f22 2009-07-12 17:17:35.021035) Hmm - doesn't help me :) christian -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=36874#36874 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
