You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "Bram de Kruijff (JIRA)" <ji...@apache.org> on 2013/05/27 09:40:57 UTC
[jira] [Reopened] (ACE-174) Configuration artifacts can not be
updated due to infinite cache
[ https://issues.apache.org/jira/browse/ACE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bram de Kruijff reopened ACE-174:
---------------------------------
> Configuration artifacts can not be updated due to infinite cache
> ----------------------------------------------------------------
>
> Key: ACE-174
> URL: https://issues.apache.org/jira/browse/ACE-174
> Project: ACE
> Issue Type: Bug
> Affects Versions: 0.8.0-incubator
> Reporter: Bram de Kruijff
> Attachments: ACE-174-weak-refs.patch
>
>
> updating (or even drop/create) configuration artifacts is not being propagated to targets. This is caused by the fact that the VelocityArtifactPreprocessor internally caches the bytes indefinitely (at least tight to the onfiguration helper service lifecycle) using the configuration artifact's url as the key. As a result checks on "needsNewVersion"will typically result in false. Furthermore, please note that the cache implementation is a threat to memory resources as no weak references are being used.
> http://www.mail-archive.com/ace-dev@incubator.apache.org/msg01345.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira