Am Sonntag 19 Oktober 2008 09:28:25 schrieb Dieter Maurer: > Hermann Himmelbauer wrote at 2008-10-17 23:04 +0200: > >During testing, I found the following warnings/errors in my zope log: > > > >------- > >2008-10-17T17:56:50 WARNING ZopePublication Competing writes/reads at ???: > >database conflict error (oid 0x06d3, class zc.queue._queue.BucketQueue, > >serial this txn started with 0x0379451cbf5d7bdd 2008-10-17 > > 15:56:44.851212, serial currently committed 0x0379451ccd1f50bb 2008-10-17 > > 15:56:48.075545) ------ > >2008-10-17T17:58:10 ERROR txn.1121233232 Error in tpc_abort() on manager > ><zope.sqlalchemy.datamanager.SessionDataManager object at 0x35a4f50> > >Traceback (most recent call last): > > ... > >line 82, in tpc_abort > > raise TypeError("Already committed") > >TypeError: Already committed > >------ > >2008-10-17T17:58:10 WARNING ZopePublication Competing writes/reads > >at /BSPSite/act/@@/bspskin-res/bankaustria.gif: database conflict error > > (oid 0x06e3, class zope.session.session.SessionData) > >------ > > > >Why is this happening? I have to admit, that I'm currently > >testing/implementing background tasks with lovely.remotetask - perhaps > > this is the reason? Perhaps it's the combination with zope.sqlalchemy? > > There have been problems with the (then) released version of > "zope.sqlalchemy" (discussed in this mailing list). > > These problems are said to be fixed in the "svn" version. > > Do your problems also occur with the "svn" version?
Ah, that could be the reason. I used zope.sqlalchemy 0.3, now I upgraded to the SVN-version, hopefully the errors will be gone. Thanks! Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )