Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

Hello, Daniel. Thanks, that's a good suggestion! I've just changed it . Cheers. On 20/04/11 15:09, Daniel Holth wrote: > I notice you begin building the query with one dbsession which must be > a Sco

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

I notice you begin building the query with one dbsession which must be a ScopedSession, then call dbsession.remove(), and then execute the query. It would probably be better to put dbsession.remove() at the top of the function. -- You received this message because you are subscribed to the Goo

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

Gustavo, thanks so much for the updates. Our initial tests on a test system seem to show that the issue is gone. We're rolling out to the production systems that are using the normal default timeout and will test if the issue is 100% gone then. Rick (mitechie) -- You received this message be

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

Hello, I finally got some time today to investigate this further and fix it. I think the only way to solve this at the repoze.who.plugins.sa level is by rolling back the transaction *before* issuing a query. I agree that, ideally, this would've been handled in the repoze.who-friendlyform plugin

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

Edwin, we're seeing a similar thing here and I've been trying to modify the form plugin to add a .remove() manually to see if it helps with little success. Can you verify that your wsgi wrap does work and can you share the code/what it's doing? Are you just importing from the models Session an

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

On Wed, Dec 22, 2010 at 2:48 AM, edwincheese wrote: > Hi > > Sorry for bringing back this rather old thread. I am going to add some > more information on the discussion of this issue. > > We have constantly encountered the exactly same issue mentioned by > Josh with Pylons and repoze.who 1.0 in a

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

Hi Sorry for bringing back this rather old thread. I am going to add some more information on the discussion of this issue. We have constantly encountered the exactly same issue mentioned by Josh with Pylons and repoze.who 1.0 in a low traffic web application. After analysed the check out pattern

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

On Nov 18, 5:05 pm, Gustavo Narea wrote: > If I make repoze.who.plugins.sa handle the exception, I'd be silencing > that error, which I'd rather not do as that sort of things always make > debugging harder. Sorry if I wasn't clear enough. I was suggesting doing something like except:

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

Hello, Josh. On Nov 17, 4:34 am, Josh Kelley wrote: > On Nov 16, 5:45 pm, Gustavo Narea wrote: > > > Thanks for the information. > > > I couldn't find the message "Can't reconnect until invalid transaction > > is rolled back" in the output you pasted and I think the link to the > > FAQ refers to

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

On Tue, Nov 16, 2010 at 8:34 PM, Josh Kelley wrote: > On Nov 16, 5:45 pm, Gustavo Narea wrote: >> Thanks for the information. >> >> I couldn't find the message "Can't reconnect until invalid transaction >> is rolled back" in the output you pasted and I think the link to the >> FAQ refers to anoth

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

On Nov 16, 5:45 pm, Gustavo Narea wrote: > Thanks for the information. > > I couldn't find the message "Can't reconnect until invalid transaction > is rolled back" in the output you pasted and I think the link to the > FAQ refers to another type of issue. Sorry. There are actually two exceptions

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

Hello, Josh. Thanks for the information. I couldn't find the message "Can't reconnect until invalid transaction is rolled back" in the output you pasted and I think the link to the FAQ refers to another type of issue. According to the traceback, the exception is raised when the user object is lo

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

On Nov 15, 4:54 pm, Gustavo Narea wrote: > The only thing I can think of is that the repoze.who middleware was > added in the wrong order. Please have a look at this > example:https://bitbucket.org/Gustavo/whatpylonsproject/src/tip/pylonssecured... > > I don't remember seeing that error before. C

Re: "Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

Hello, The only thing I can think of is that the repoze.who middleware was added in the wrong order. Please have a look at this example: https://bitbucket.org/Gustavo/whatpylonsproject/src/tip/pylonssecuredapp/config/middleware.py I don't remember seeing that error before. Can you please paste th

"Can't reconnect until invalid transaction is rolled back" with repoze.who / repoze.what

I'm getting the dreaded "MySQL server has gone away" and "Can't reconnect until invalid transaction is rolled back" pair of errors in my Pylons application. >From what I've read online, the "Can't reconnect until invalid transaction is rolled back" is supposed to be avoided by Pylons' default lib/