You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@archiva.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2014/08/08 06:33:10 UTC

[jira] (MRM-483) verify thread safety of Configuration object

     [ https://jira.codehaus.org/browse/MRM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MRM-483:
-----------------------------

    Fix Version/s:     (was: 2.1.1)
                   2.1.2

> verify thread safety of Configuration object
> --------------------------------------------
>
>                 Key: MRM-483
>                 URL: https://jira.codehaus.org/browse/MRM-483
>             Project: Archiva
>          Issue Type: Bug
>            Reporter: Brett Porter
>             Fix For: 2.1.2
>
>
> 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.1.6#6162)