[zope2-tracker] [Bug 142129] Re: THUNKED_TM mismatch with TM.TM

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brad Clements wrote:
> We are using gvibDA and Firebird.
> 
> The patch from 2001 is for Zope 2.5.
> 
> I see we're currently running Zope 2.7.2-0 and it does not have the
> THUNK.py patch applied.
> 
> However we're running all our Zope instances in single-threaded  mode
> due to unreliability with the DB adapter.
> 
> Interesting, I think when upgrading from 2.5 to 2.7.2 we forgot to re-
> apply our suggested patch. Then Zope got  unreliable and instead of
> figuring it out again and applying the patch, we just moved to single-
> threaded mode behind Pound.
> 
> ---
> 
> The point of the patch is to make sure that changes to self._registered
> occur only while the lock is held. Without this change the THUNKED_TM
> instance can appear as still being registered even when it is no longer
> registered due to the lock being released (thereby allowing another
> thread to pick up the THUNKED_TM instance) before self._registered is
> set to 0

I think I get the point:  my worry is that I don't use any "thunked"
database adapter myself, and wouldn't have a way to know that I broke
something,

I know you guys are still running a 2.7.x Zope:  would you be able to
test the gvibDA against a 2.12 branch checkout?  I will try installing
firebird2.1-classic on my machine and see if I can at least connect and
run SQL queries.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkvPkSgACgkQ+gerLs4ltQ4lCQCeJPGUx8UUptML1JBAviFvO/tL
fwUAniPih8WKtoWpIDnryT5kk/Rs4y34
=T7Lk
-----END PGP SIGNATURE-----

-- 
THUNKED_TM mismatch with TM.TM
https://bugs.launchpad.net/bugs/142129
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.