Hi Michael, I figured out the problem. It was a connection sharing issue. Looks like different connection objects were getting returned from the pool (which was created using the creator approach in create_engine()) when relations were getting loaded as a part of processing. Due to this sometimes connection swapping was happening among the different request threads.
I resolve this I created a threadsafe QueuePool and passed a class wrapping the same while creating engine. This helps the same connection getting returned for the same thread. Programming error! Hopefully I have tested everything and this does not crops up again :) Thanks for the support! - A On 7/13/07, Arun Kumar PG <[EMAIL PROTECTED]> wrote: > > Sure Michael I will get back on this in a while as I am researching on > this. Thanks for your support. I hope this gets resolved sooner as I am very > much dependent on this and the application is really critical and should be > up in next couple days! > > Thanks and i will get back on this in next couple hours. > > On 7/13/07, Michael Bayer <[EMAIL PROTECTED] > wrote: > > > > > > also send along a full stack trace so at least it can be seen where > > this is occuring. > > > > > > > > > > > > > -- > Cheers, > > - A -- Cheers, - A --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
