> hanging things up. It ended up being a problem when accessing the > environ somewhere in my template which I had been doing for debugging > purposes.
Interesting.. Were you running in debug mode as well?. I noticed a few failed get requests (way back in my logs) resulting from some missing static image files served from the public directory. It appears that when the StaticURLParser was unable to find the image, the Cascade called the app and the request was resolved successfully to a controller action - which failed (cos the image filename resolved to a route variable in a matched route and the resulting action was trying to query the db using the image filename as a primary key). :). Duh!. I will have to revisit my route map perhaps, and make the controller more bullet-proof!. This apparently is the only indication of what the problem can be. Incidentally I was running in debug mode each time. The pylons logs showed the link for debugging each instance of these failed get requests, however the parent get request (that resulted in the failed secondary request to get an image) was processed succesfully otherwise and the response was'nt intercepted by the ErrorHandler (at the time) to display the interactive debugger- as a result I didnt notice this until after the fact. So I didnt inspect the failures at the time. Why wasnt the pylons interactive debugger triggered in this case since I dont have any code in the controller action to explicitly handle this failure.? The bigger question is can a sequence of these failures cause the application to freeze? > problem in a fairly rigid way, in other words I kept on putting > log.debug in until I was able to determine exactly where it was > hanging. I will certainly do this. Thanks. On Aug 26, 8:36 pm, "Thomas G. Willis" <[email protected]> wrote: > 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. > > FWIW, i was seeing some hanging in a site I was hacking a while back, > and I thought that maybe it was some middleware I wrote that was > hanging things up. It ended up being a problem when accessing the > environ somewhere in my template which I had been doing for debugging > purposes. It took me a while to figure it out but I approached the > problem in a fairly rigid way, in other words I kept on putting > log.debug in until I was able to determine exactly where it was > hanging. So maybe start at the controller method and work your way > back through the call stack. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
