Rickard,
Thanks for the explanation, and your patience with me :-).
I really like the idea, from an administrators point of view, being able
to change server configuration dynamically, without having to cycle it.
That is a very powerful feature that many application servers, even
commercial servers, don't do or don't do well.
However, I'm not sure I like the idea that dynamic changes, which might
be made due to specific load conditions, would automatically be reflected
in the static configuration. Since jboss.jcml is dynamically
synchronized with jboss.conf, and jboss.jcml has static information such
as datasource pool size, username, password, etc, it makes it very
confusing and difficult to administor. I would recommend that all static
information be kept in a separate configuration file, and maybe even
reconsider trying to persist dynamic changes to the server configuration,
or simply record such information in separate log file(s) so that
administrators can use this information to make purposeful decisions
about the static configuration of the server.
Well, thats my .02 worth. jBoss is a great EJB server. Thanks again for
your patience and for the explanation. Keep up the great work.
Scot.
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 11/30/00, 10:25:22 AM, Rickard �berg <[EMAIL PROTECTED]> wrote regarding
Re: [jBoss-User] jboss.jcml getting corrupted!:
> Hi!
> Scot Bellamy wrote:
> > I'll have to go and look at some of the discussions surrounding this. I
> > have two major concerns about this.
> >
> > 1. The stability of the system. Even when the Mbeans that are
> > corrupting the file are fixed, later enhancements can cause the same
> > problem all over again. I worry about the overall stablity of jBoss with
> > such a design/implementation.
> >
> > 2. The ability of system administrators to administor a system where the
> > configuration files are changing dynamically. Simply cycling the server
> > can change its behavior, even if configuration changes are not
> > purposefully changed by the administrator.
> >
> > I realize that I might be talking out of ignorance as many of the
> > discussions regarding jboss.jcml probably occurred before I joined the
> > list a couple of months ago. I will look through the archives and try to
> > better understand the purose of doing it this way.
> The basic purpose is to make sure that jboss.jcml mirrors the actual
> settings of all MBeans in the server. This means that if you add MBeans
> to jboss.conf then the initial state of those must be written to
> jboss.jcml. Similarly, if you remove MBeans from jboss.conf those must
> be removed from jboss.jcml. So, it's a synch operation mainly.
> Additionally, we will later change the configuration management so that
> changes to MBeans through a remote administration interface is persisted
> to jboss.jcml so that any such changes survive a server restart.
> While I understand that most people currently administer JBoss by
> directly editing jboss.jcml I do not think this will be the common
> practice in the future when the configuration and remote administration
> tools are more developed.
> regards,
> Rickard
> --
> Rickard �berg
> Email: [EMAIL PROTECTED]
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
