[
http://jira.codehaus.org/browse/MRM-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125725
]
Michael Sell commented on MRM-526:
----------------------------------
I am in an environment where my major central mirror goes down somewhat often.
Whenever it does my builds essentially hang because of the long timeouts in
Archiva. If this feature is to make the timeouts "easily" configurable, how
does one do it the hard way right now? It also seems that Archiva should
perhaps cache that a remote repository is unreachable and not force every
request to timeout individually. As it is, to keep my builds going I have to
change my proxy url every time the remote repository goes down just to point to
something else that I know is up to avoid the timeouts.
> cache-failure policy timeout should be easily configurable
> ----------------------------------------------------------
>
> Key: MRM-526
> URL: http://jira.codehaus.org/browse/MRM-526
> Project: Archiva
> Issue Type: Improvement
> Components: remote proxy
> Affects Versions: 1.0-beta-2
> Reporter: JR Boyens
> Fix For: 1.x
>
>
> set in a plexus.xml deep in archiva-policy.jar
--
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
