Steve,The fortress configuration utility uses apache commons configuration to combine properties found in both config files (bootstrap config) and ldap node. While the commons config utility has the capability for periodic refresh of properties, fortress does not currently use it. This means a restart of fortress runtime is required to force new values to be available.
I am not opposed to modifying this behavior in the future. Will need to take a look at effort but do not expect it to be a big deal.
Thanks, Shawn On 09/05/2013 12:03 PM, Steven W. Moyer wrote:
I am using the ConfigMgr to maintain the configuration for one of our Fortress applications and am having a problem with the synchronization of the configuration information between different nodes of the cluster (all backed by the same OpenLDAP system). Is the Fortress client caching configuration information? What kind of lag time can I expect (between one node executing a configMgr.update(...) and another node "seeing" that update via configMgr.read(...). Thanks! Steve
-- Shawn McKinney shawn.mckinney@jts.us