[ZCM] [ZC] 472/ 3 Defer "THUNKED_TM mismatch with TM.TM"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #472 Update (Defer) "THUNKED_TM mismatch with TM.TM"
 Status Deferred, Zope/bug+solution medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/472

==============================================================
= Defer - Entry #3 by tseaver on Apr 11, 2005 1:55 pm

 Status: Pending => Deferred

I can't think of a good way to test this.  Does it still apply to
the Zope / RDB you work with (I hope that is Zope 2.7)?

Without followup, reject in two weeks.
________________________________________
= Comment - Entry #2 by bkc on Jul 15, 2002 1:28 pm

Just wanted to comment about the tpc_abort = abort line at the end of the class.

TM.TM has a similar statement. Since we re-define the abort function, I can't help but feel that tpc_abort still points to the base class (TM.TM) version of abort, not the THUNKED_TM version of abort.

Hence, I added the tpc_abort = abort line. Is that correct?
________________________________________
= Request - Entry #1 by bkc on Jul 15, 2002 1:24 pm


Uploaded:  "THUNK.py.diff"
 - http://www.zope.org/Collectors/Zope/472/THUNK.py.diff/view
THUNKED_TM doesn't seem to have kept pace with TM.TM, with respect to using _finalize instance variable. Also, it releases the lock before setting the instance's registered property to 0, which under heavy load can cause the instance to be re-used without being re-registered.

Here's a patch.
==============================================================