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.
Scot.
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 11/30/00, 9:29:08 AM, Vaughn Vernon <[EMAIL PROTECTED]> wrote regarding
Re: [jBoss-User] jboss.jcml getting corrupted!:
> Howdy,
> > I think this goes back to discussions from yesterday
> > about the jboss.jcml file being written by jBoss
> > during server startup. The kind of corruption you
> > describe is exactly the risk of such a design. I
> > hope someone on the jBoss development team changes
> > this soon! Configuration files should NEVER be
> > written by jBoss. Any descriptive information that
> > needs to be written should go in log files that are
> > not read by jBoss.
> >
> > Scot.
> Obviously someone thinks it's ok ;-)
> If you think of the .jcml as being an INI file (sorry)
> or a registry, then it makes sense. Ini files get
> configured and they also get written to. At least
> jboss locks the file. In the Windows ini days, the
> last writter wins!!!
> Don't know if you have a case here. :-)
> Vaughn
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Shopping - Thousands of Stores. Millions of Products.
> http://shopping.yahoo.com/
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
