You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2005/09/14 11:27:00 UTC
DO NOT REPLY [Bug 36652] New: -
configuration hot-reload may corrupt configuration
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36652>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36652
Summary: configuration hot-reload may corrupt configuration
Product: Commons
Version: 1.1 Final
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Configuration
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: ndeloof@capgemini.fr
Current reloading process clears current properties and load updated values from
resource reader. If an IO error occurs (or invalid format), the configuration
gets corrupted and the application becomes unstable.
It may be better for hot-reload to put loaded values into a temporary Properties
and replace previous values only when reloading is successful.
It may also allow to use a 'currentlty-reloading' flag in the synchronized
'reload' block to avoid blocking threads during a reload (they could access
safelly the 'old' properties until reload is finished)
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org