verify thread safety of Configuration object
--------------------------------------------
Key: MRM-483
URL: http://jira.codehaus.org/browse/MRM-483
Project: Archiva
Issue Type: Bug
Reporter: Brett Porter
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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
