Re: [Zope-dev] zope transaction bug?
Ross J. Reedstrom writes: Boy, it's been a long time since I've hung around here. Anyway, I think we've found a bug somewhere in the zope transaction machinery. A really long time ago someone reported (just once) a bug in Zope's transaction system. When I remember right, the problem occured when there was an exception in the late stages of transaction processing. This caused Zope to forget about aborting some other transactions. Not sure, whether this problem is still in modern Zope versions. Not sure, whether it is your problem... Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope transaction bug?
On Fri, Mar 08, 2002 at 08:55:56PM +0100, Dieter Maurer wrote: Ross J. Reedstrom writes: Boy, it's been a long time since I've hung around here. Anyway, I think we've found a bug somewhere in the zope transaction machinery. A really long time ago someone reported (just once) a bug in Zope's transaction system. When I remember right, the problem occured when there was an exception in the late stages of transaction processing. This caused Zope to forget about aborting some other transactions. Not sure, whether this problem is still in modern Zope versions. Not sure, whether it is your problem... Sounds similar, however we get it on rollback (Undo) regardless if the Undo succeeds or not. Errors during normal 'forward' use seem to abort correctly, _even after_ the connection gets in a bad state. So, I'm guessing that the earlier problem may have been masked by a fixup that we're now going around, in some way. Ross ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope transaction bug?
On Fri, Mar 08, 2002 at 04:12:31PM -0600, Ross J. Reedstrom wrote: On Fri, Mar 08, 2002 at 08:55:56PM +0100, Dieter Maurer wrote: Ross J. Reedstrom writes: Boy, it's been a long time since I've hung around here. Anyway, I think we've found a bug somewhere in the zope transaction machinery. A really long time ago someone reported (just once) a bug in Zope's transaction system. When I remember right, the problem occured when there was an exception in the late stages of transaction processing. This caused Zope to forget about aborting some other transactions. Not sure, whether this problem is still in modern Zope versions. Not sure, whether it is your problem... Sounds similar, however we get it on rollback (Undo) regardless if the Undo succeeds or not. Errors during normal 'forward' use seem to abort correctly, _even after_ the connection gets in a bad state. So, I'm guessing that the earlier problem may have been masked by a fixup that we're now going around, in some way. Further testing seems to indicate that there needs to be at least one failed Undo attempt: after that, _any_ undo will trigger it. Ross ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] zope transaction bug?
Hey all - Boy, it's been a long time since I've hung around here. Anyway, I think we've found a bug somewhere in the zope transaction machinery. Every now and then, a backend will get into 'idle in transaction' state. After that, no work on that backend ever commits - the 'END' query just never gets sent. Careful analysis of the log files indicated that the ZpsycopgDA instance started 'losing' proper transactional control after an admin who was logged in via an exUserFolder that _also_ used that DA for authentication used the management interface to undo a Zope transaction. The transaction in question was merely an edit on a DTML file. No db interaction beyond the authentication. Either a successful or an unsuccessful attempt to rollback causes the problem. Seems the Zope transactional machinery has 'forgotten' that our connection needs to be told about transaction boundries. We can make this happen at will, with Zope 2.4.3 or 2.5.0, exUserFolder 0.10.7, and ZpsycopgDA 1.0.5. It does require using the usAuth (User Supplied Auth source) part of exUserFolder. Our developer who's somewhat familiar with the guts of exUserFolder thinks that this is probably still a bug in Zope, since all usAuth does is use customized ZSQL methods to change where various strings are stored in the DB. We're seeing similar problems with ZpopyDA, but haven't tested it thoroughly to see if it's the same trigger. I've constructed the test case for this: it's available at: http://wallace.ece.rice.edu/xact-bug.tar.gz That tarball contains an SQL schema script, zexp, and minimal instructions for replicating the problem. Anyone have any clues as to where to look to fix this? We're losing commits to our database, whenever a developer tries to Undo something: not good! Ross -- Ross Reedstrom, Ph.D. [EMAIL PROTECTED] Executive Director phone: 713-348-6166 Gulf Coast Consortium for Bioinformatics fax: 713-348-6182 Rice University MS-39 Houston, TX 77005 ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
