On Thursday 16 October 2008 00:38:48 Graham Dumpleton wrote: > On Oct 15, 11:09 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote: > > I assume there is no chance to drop the apache into the PDB... so I will > > need to have to investigate this via turning on logging inside the > > TG-app. > > Yes you can use pdb if you really need to. See: > > > http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Python_Interactiv >e_Debugger
Thanks, I should have read the docs more careful. I did solve the problem - sort of. It has nothing to do with mod_wsig. Instead, some laziness on TG2/Pylons/Whomever's behalf is the culprit. The thing that happens is pretty simple: to serve static resources outside TW, they need to be registered. This happens inside the controller-modules (widgets are supposed to be globally declared, not instantiated on a per-request-base) Now if a request hits a process that hasn't served any controller-based url, the whole controller-hierarchy isn't loaded. Thus no registration, and thus the 404. Naturally the problem would go away once you put enough load on the system so that all processes are hit by an actual controller-served request. Obviously that can't be a solution, as it would mean that the first few dozen users or so get errors. I will investigate what can be done. Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
