> 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?
This event occured a few times (during busy periods) on a live intranet service while users were on the system. In order to restore service quickly I had to restart the app without the benefit of having closely inspected the app while it was in the frozen state. However in one case it appeared that requests from the browser were reaching the server and the server was simply not responding. This led me to initially believe that perhaps request threads might be hanging. However this theory does not appear to be supported by the kill_hung_thread messages which indicated that there were many idle threads running. In fact I increased the thread pool size from 10 to 50 but this made no difference - it happened again a few days later. > I'd certainly agree with that assessment. If there is a hang going on, that > message isn't giving you any help. Yes. My preliminary assessment is that the "kill_hung_thread" message is totally unrelated On Aug 26, 5:58 pm, Mark Hildreth <[email protected]> wrote: > On Wed, Aug 26, 2009 at 5:24 PM, afrotypa <[email protected]> wrote: > > > Hmmm. I am not sure how to figure this one out. There are many of > > those messages; and the app certainly *did not* hang each time the > > "kill_hung_message" was generated. Perhaps that message is a red > > herring and I should be looking at something else. > > > Any ideas? > > I'd certainly agree with that assessment. If there is a hang going on, that > message isn't giving you any help. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
