> Correct. From what you've described, I wouldn't have thought that the > reload setting would be enabled, as otherwise every request would > initiate a reload. You mentioned that the slowdown/error is happening > every hour, which leads me to wonder if there isn't a scheduled task > or something along those lines that is hitting the application with > the reload key/password in the URL and thereby triggering the reload.
There shouldn't be any scheduled tasks that run more than once a day, and none of them force a reload (and to be clear, "every hour" was a rough approximation of frequency rather than scheduling). But just to be thorough, I went and changed the reload password for the app. > > > Your comment regarding waiting requests makes me wonder if perhaps my > > authentication request is taking too long. Part of the authentication > > event involves redirecting the user outside of the app to our Common > > Authentication Server (CAS), and CAS then comes back to the > > authentication event with the result, so if the event is essentially > > waiting for that turnaround and that time is applied to the lock, then > > maybe that could also be part of the problem. I've upped the lock > > timeout to 90 seconds to see if that helps as well. > > Your application code wouldn't have any effect on this particular > problem, as the phase loading happens before a requested event is > processed. Once loading of the configuration phase is complete, that > lock will be released, and any waiting requests will be able to > proceed, so if the timeout error is occurring there, then the XML > config loading would be the culprit. As this is generally the most > expensive part of the reloading process, that would certainly make > sense. Thanks for clarifying. So the XML config in this case are my ModelGlue XML files that denote the event-handlers, controllers, etc.? And they're only loaded during the startup/reload of ModelGlue? Which would mean it comes back to this idea that somehow the app is getting reloaded more often that it should. The lifespan of MG should be as long as the lifespan of the application scope, which is currently set to 2 days. Puzzling. > > If you could give me a copy of that beta so I can have that as an "if > > all else fails" option, that would be great. > > Sure, I'll send you a zip of the code off-list, with the caveat that > you will of course want to test this very thoroughly before deploying > it live. Yes, I will make sure it works before putting it in production (and hopefully it won't come to that). --Brian -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en
