[
https://issues.apache.org/jira/browse/MRM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Stockhammer updated MRM-483:
-----------------------------------
Fix Version/s: (was: 2.2.2)
3.0.0
> verify thread safety of Configuration object
> --------------------------------------------
>
> Key: MRM-483
> URL: https://issues.apache.org/jira/browse/MRM-483
> Project: Archiva
> Issue Type: Bug
> Reporter: Brett Porter
> Fix For: 3.0.0
>
>
> Deng discovered a thread-safety bug in the re-initialisation of the
> Configuration object when saving and consequently re-initialising. While that
> has been fixed, and DefaultArchivaConfiguration is now thread safe, it does
> pass out the shared Configuration object. We need to audit places that the
> object may be modified in a way that is not thread safe (if it is being
> modified, it should not be used by another thread until the save() method has
> completed and those threads have called get() again - perhaps anything that
> intends to modify it should get back a copy of the configuration object
> instead).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
