On Thursday, August 12, 2010 11:21:10 Guyren G Howe wrote: > On Aug 12, 2010, at 1:00 , Diez B. Roggisch wrote: > > Nothing that *you* wrote? So far, I haven't see anything called "eagle" > > in my stacktraces. Including a "eagle.middleware". > > > > All I can say is: it works for me, and others. So I'm inclined to say: > > it's something you do. > > > > "repoze.tm" is the responsible middleware for opening/closing > > transactions. And usually does it's job. > > > > But only if the model code properly sets up the session. > > > > I suggest you quickstart a new project with authorization enabled (to > > have some DB-model), add a simple controller method that queries this > > model, and see if it happens to you there as well. If not, try & see > > what you do different in setting up your model. Or in your middlewares. > > Quite right, my bad. > > But note that this isn't the point where the failure occurs. This is the > point where I notice the failure because I've got six transactions backed > up on the server and it refuses to start a seventh. So the actual point of > failure is the point where it fails to close a transaction during the > previously apparently successful execution of my code. And this, as I say, > the documentation seems to say shouldn't be possible.
I'm well aware what the docs & you say. But don't you think that a general 6- requests-limit for TG2 apps would have been noticed? And I don't read in the docs "we guarantee you will never run out of transactions whatever you do, including a call to 'mess_up_orm_layer()'". Whatever you do in your code, it makes SA *not* close the transaction when the repoze.tm middleware asks it to do so. I don't know what could be the reason for this (especially as you don't provide any code), but I *do* know that it's not the way TG2 behaves in general. So did you actually try my suggestion of tracking potential changes you did to the SA-setup? Diez -- 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?hl=en.
