Hi, Ezra, Thanks for responding.
So if I understand you correctly, the loading process that uses this lock should only be invoked if the application is being loaded/ reloading, as if the reload function of ModelGlue was invoked? I just double-checked my MG config: reload was set to "false" as expected, but it does look like I goofed and forgot to reset debug back to "false" after I did a quick debugging check last week: that probably didn't help matters. 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. 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. --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
