I was waiting to see if there was a recurrence before getting back on this.
I havent seen the app hang since I fixed the failure on the secondary get request (a la missing image files). So I will go out on a limb to declare victory on this one. However, I am still curios as to the precise mechanics of how the hanging ensued. My lingering question is :- Are there scenarios in which paste will report hung threads as idle? Or is this undesirable behaviour somewhat peculiar to running in debug mode?. I am hard-pressed to come up with a logical explanation for this behaviour... Does anyone have a reasonable explanation for this or am I missing some crucial fact here?. On Aug 27, 6:57 am, afrotypa <[email protected]> wrote: > > There may be a genuine hanging in afrotypa's case, but whether it's > > related to the ThreadPool is another question. Ranjan had a similar > > problem on May 18: > > The app is certainly freezing in my case. > > I saw Ranjan's post earlier and considered replying with my own > experience. For some reason there was only a reply to author link. So > I decided to create a new discussion for all eyes to see... > > Thanks, > On Aug 27, 12:18 am, Mike Orr <[email protected]> wrote: > > > On Wed, Aug 26, 2009 at 2:34 PM, Mark Hildreth<[email protected]> > > wrote: > > > On Wed, Aug 26, 2009 at 3:45 PM, afrotypa <[email protected]> wrote: > > > >> I keep getting messages similar to these > > >> "14:33:03,987 INFO [paste.httpserver.ThreadPool] kill_hung_threads > > >> status: 50 threads (0 working, 50 idle, 0 starting) ave time N/A, max > > >> time 0.00sec, killed 0 workers" > > > >> At which point my app hangs and needs restarting. > > > > When you say it "hangs", what specifically do you mean? When you try to > > > access a page after seeing this in the logs, what response do you get > > > back? > > > > The message you're seeing is a logging message from the paste http server. > > > After X number of requests (the default is 100), the server will check all > > > the running threads and see if any of them have been running "too long". > > > It > > > would consider these still-running threads as hung, and you would've seen > > > additional logs for their killing. The logs you've shown, however, shows > > > the > > > typical result: all your threads are idle (waiting for a request to come > > > along for them to work on), and no threads needed to be killed. > > > Added to the FAQ. > > >http://wiki.pylonshq.com/pages/viewpage.action?pageId=2392095 > > > There may be a genuine hanging in afrotypa's case, but whether it's > > related to the ThreadPool is another question. Ranjan had a similar > > problem on May 18: > > > "While running a TG2 application from console, often I get the > > following message and then the application hangs: [same message]. > > Then, again I need to press Ctrl-C and restart my application." > > > I have no record of any followup in my mailbox, and the thread is not > > archived in the Google Group, so I don't know if it was ever resolved. > > > -- > > Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
