On Aug 10, 2006, at 7:09 PM, Jason Chu wrote: > Ok, this one took me a bit to track down. > > The version of SQLObject TG uses has a threading bug in it. If a > SQLObject class' __init__ method throws an exception (any time there's > a constraint violation or, where we ran into it, unicode encode/decode > errors), trying to instantiate any other SQLObject class in a > different > thread locks SQLObject, which locks the request, which locks the > thread. At this point all accesses to the app server hang. > > I'm pretty sure many people have run into this in production.
Yep: http://tinyurl.com/s6obo http://tinyurl.com/pfpjp > A fix was applied to the SQLObject 0.8 branch. > > The patch was applied to the SQLObject 0.7-bugfix branch too, but > hasn't > been distributed with the most recent version of TG. If you ask me, > this is a big enough problem that a new release should be pushed > through pretty quickly (maybe just updating the version of SQLObject > that's available is good enough and people can -U it). I was pretty sure TG was using the correct version but I guess it's only the 1.0 branch that has the correct svn:external. If the 0.9a8 egg has the wrong dependency defined I'm +1 on an version bump to 0.9a9. As I've mentioned in the other thread: my faut. I'm sorry this has caused so many headaches to so many people :( Alberto --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
