On Wednesday, November 7, 2012 5:48:24 PM UTC-8, Dan Wilson - [email protected] wrote: > > I believe that takes place in ModelGlue.cfm > > The lock is exclusive and is double checked as is best practice. > > However, I don't believe your parent bean factory is under that same lock. > So when you remove that bean factory, it's out of the protected zone, thus > problems arise, no? >
Correct - the exclusive named lock only prevents duplicate initializations; it doesn't do anything related to non-reinit MG requests from accessing values/objects that are changing during the initialization like the parent bean factory. We need a method of telling MG to lock/unlock access to the parent bean factory while we reinit it. An exclusive lock on the app scope might do it? I don't know if that would be hard to obtain in practice in production or if it would just cause a lot of timeouts? 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
