geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Questions on Geronimo's var directory and the config-store directory
Date Mon, 11 Jul 2005 13:22:15 GMT
Is this statement correct.. The "var" directory intended for holding data 
specific to a particular Geronimo instance and not intended to be shared 
by multiple instances of geronimo?

If I wanted to run two geronimo instances, sharing the same installation 
directory (e.g. so geronimo\lib and geronimo\repository is shared), each 
of the two instances of geronimo would need to be started with a unique 
geronimo.base.dir property value ?

Currently Geronimo's "config-store" directory is a child of the Geronimo 
installation directory rather than a child of the"var" directory (which is 
relative to geronimo.base.dir).  What is the reason for config-store not 
being under the var directory?  Is it because it is just a file 
implementation of a config store and could change in the future to some 
other storage implementation?

If the config-store is being shared by multiple instances of Geronimo 
couldn't that pose a problem when two instances using the same 
configuration are updated when a server shuts down?

Does anyone have thoughts on how deployment and loading of configurations 
would work in the future when Geronimo supports clustering and how it 
would work with a config store? 



This e-mail message and any attachments may contain confidential, 
proprietary or non-public information.  This information is intended 
solely for the designated recipient(s).  If an addressing or transmission 
error has misdirected this e-mail, please notify the sender immediately 
and destroy this e-mail.  Any review, dissemination, use or reliance upon 
this information by unintended recipients is prohibited.  Any opinions 
expressed in this e-mail are those of the author personally.

View raw message