[jira] [Updated] (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henning Schmiedehausen updated CONFIGURATION-136: - Fix Version/s: (was: 1.10) > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Attachments: commons-configuration-1.5_patch_CONFIGURATION-136.jar, > commons-configuration-1.8_patch_CONFIGURATION-136.jar, patch.txt > > > 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) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurent Michelet updated CONFIGURATION-136: --- Attachment: patch.txt Maybe it's because I get used to work with proprietary source code ;-) > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.9 > > Attachments: commons-configuration-1.5_patch_CONFIGURATION-136.jar, > commons-configuration-1.8_patch_CONFIGURATION-136.jar, patch.txt > > > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurent Michelet updated CONFIGURATION-136: --- Comment: was deleted (was: Patch for CONFIGURATION-136 based on a 1.8 release) > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.9 > > Attachments: commons-configuration-1.5_patch_CONFIGURATION-136.jar, > commons-configuration-1.8_patch_CONFIGURATION-136.jar > > > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurent Michelet updated CONFIGURATION-136: --- Attachment: commons-configuration-1.8_patch_CONFIGURATION-136.jar Patch for CONFIGURATION-136 based on a 1.8 release > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.9 > > Attachments: commons-configuration-1.5_patch_CONFIGURATION-136.jar, > commons-configuration-1.8_patch_CONFIGURATION-136.jar > > > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurent Michelet updated CONFIGURATION-136: --- Attachment: (was: commons-configuration-1.8_patch_CONFIGURATION-136.jar) > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.9 > > Attachments: commons-configuration-1.5_patch_CONFIGURATION-136.jar > > > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurent Michelet updated CONFIGURATION-136: --- Attachment: (was: commons-configuration-1.5_patch_CONFIGURATION-136.jar) > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.9 > > Attachments: commons-configuration-1.5_patch_CONFIGURATION-136.jar > > > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurent Michelet updated CONFIGURATION-136: --- Comment: was deleted (was: Patch for CONFIGURATION-136 based on a 1.5 release) > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.9 > > Attachments: commons-configuration-1.5_patch_CONFIGURATION-136.jar, > commons-configuration-1.5_patch_CONFIGURATION-136.jar, > commons-configuration-1.8_patch_CONFIGURATION-136.jar > > > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurent Michelet updated CONFIGURATION-136: --- Attachment: commons-configuration-1.5_patch_CONFIGURATION-136.jar Patch for CONFIGURATION-136 based on a 1.5 release > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.9 > > Attachments: commons-configuration-1.5_patch_CONFIGURATION-136.jar, > commons-configuration-1.5_patch_CONFIGURATION-136.jar, > commons-configuration-1.8_patch_CONFIGURATION-136.jar > > > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurent Michelet updated CONFIGURATION-136: --- Attachment: commons-configuration-1.5_patch_CONFIGURATION-136.jar Patch for CONFIGURATION-136 based on a 1.5 release > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.9 > > Attachments: commons-configuration-1.5_patch_CONFIGURATION-136.jar, > commons-configuration-1.8_patch_CONFIGURATION-136.jar > > > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurent Michelet updated CONFIGURATION-136: --- Attachment: commons-configuration-1.8_patch_CONFIGURATION-136.jar Patch for CONFIGURATION-136 based on a 1.8 release > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.9 > > Attachments: commons-configuration-1.5_patch_CONFIGURATION-136.jar, > commons-configuration-1.8_patch_CONFIGURATION-136.jar > > > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Heger updated CONFIGURATION-136: --- Fix Version/s: (was: 1.7) 1.8 > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.8 > > > 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) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Heger updated CONFIGURATION-136: --- Fix Version/s: (was: 1.6) 1.7 > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.7 > > > 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) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CONFIGURATION-136) Reloading may corrupt the configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated CONFIGURATION-136: - Component/s: File reloading > Reloading may corrupt the configuration > --- > > Key: CONFIGURATION-136 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-136 > Project: Commons Configuration > Issue Type: Bug > Components: File reloading >Affects Versions: 1.1 >Reporter: nicolas de loof > Fix For: 1.6 > > > 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) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
