Some more findings: > However, the behavior that putting the url in question (e.g. > http://localhost/collaborate/toscawidgets/resources/ableton.collaborate.fro >ntend/public/javascript/jquery/cluetip/jquery.cluetip.js ) into a tab, and > pressing F5 frequently would show the intermittent 404, or sometimes the > resource, seems to be gone.
This was unfortunately not true, it showed the old behavior - a non-deterministinc sequence of 200s and 404s. > So far, the resource seems to be returned all the time. > > I created a diff that I attached between two requests for the same > resource, one failing, one successful. > > As one can see, there is only very little difference, and most of the > differences are to be expected. > > 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. By now I found out that the culprit is tw.core.resources.ResourcesApp. Every now and then, it fails to enumerate the registered resources. I could confirm that this depends on the PID. If the requests hit the same PID that the app was started with, things are ok. If it hits another one, they fail. So it looks as if there are instances of the application lying around that aren't properly initialized... Currently I find this very intimidating :( 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 -~----------~----~----~----~------~----~------~--~---
