Don't panic marc, even I don't plan to implement this this week ;-) Here's the context I'm thinking about, and please note IANASA (I am not a system administrator)... but if I were running the jboss cluster at Megacorp Conglomerates, I expect my audit trail requirements would include knowing exactly what configuration was used to process each online b2b soap enabled etc purchase order, yet allow on the fly hot updates to avoid even momentary service disruptions. Also, you don't want half-completed configuration changes to start getting used - you want them to finish first. I'm just saying this point of view on requirements (if they are indeed desirable, I don't really know) is satisfied really well by the versioning transaction model of firebird/interbase: transactions get numbered as they come in, so you can tell from the log what order they happened in, and configuration changes are invisible to all transactions (invocations) that start before the configuration change commits, whereas those after the commit use the new configuration. Conceptually this seems cleaner to me than the "valves" you were talking about to stop MIs during reconfiguration.
As Rickard says, this might have a lot of overhead, and at least some of the properties of this system will come from careful use of copy on write. On 2001.10.02 12:45:31 -0400 marc fleury wrote: > > |I would like this best if the jmx server state were transactional with > |versioning optimistic concurrency control, like the firebird/interbase > db. > |In this kind of scheme, an invocation to a mbean would get a jmx > |"transactional" view of all the mbeans in the jmx server as of the start > of > |the invocation. The view of mbeans would be stable until the invocation > |finishes. Other concurrent changes to mbean state would use "copy on > |write" semantics and be visible (after they were committed) to jmx > |transactions started after the commit of the jmx modifications. After > all > |uses of a replaced mbean were complete the (now inacessible) old version > of > |the mbean can be garbage collected. Presumably one could also set up > |externally controlled jmx transactions so several configuration changes > |could occur atomically within one transaction. I guess I will have to > read > |more of the mbean spec to see if this is consistent with it ;-) > | > |Optimistic/versioning or not, I think some kind of jmx transaction to > make > |configuration invisible until it all completes will be necessary to make > on > |the fly reconfiguration plausible and not too disruptive. > > oh no... another one goes pop! > > kid, what are you talking about? please expand, does someone understand > this? > > marcf > | > | > |> > |> > We do have a "centralized" intelligence, the distributed JMX bus > (you > |> > indirect in JMX at every point) > |> > |> > |> Yup. It will be more of an interesting configuration problem, than a > |> programming/design problem. How do you get this to work without > getting > |> config files the size of the planet? :-) > | > |How is this much worse than we have now? Now we have standardjboss.xml > |with a list of interceptors: then we will have this configuration in a > |"endpoint" mbean as a list of mbean references, and also mbean > |configuration for each interceptor individually. > | > |david jencks > |> > |> /R > |> > |> -- > |> Rickard �berg > |> Software Development Specialist > |> xlurc - Xpedio Link�ping Ubiquitous Research Center > |> Author of "Mastering RMI" > |> Email: [EMAIL PROTECTED] > |> > |> > |> _______________________________________________ > |> Jboss-development mailing list > |> [EMAIL PROTECTED] > |> https://lists.sourceforge.net/lists/listinfo/jboss-development > |> > |> > | > |_______________________________________________ > |Jboss-development mailing list > |[EMAIL PROTECTED] > |https://lists.sourceforge.net/lists/listinfo/jboss-development > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
