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

Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/07/02 00:50:26 UTC

[jira] Updated: (MRM-798) blacklisting unavailable remote reps

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

Brett Porter updated MRM-798:
-----------------------------

    Fix Version/s:     (was: 1.1)
                   1.2

we currently have no way to tell what is a resource error and what is a repository error, so it is cache failures per resource. We're not tracking timeouts as separate errors.

Moving this out to do some more advanced analysis of remote state for managing connections

> blacklisting unavailable remote reps
> ------------------------------------
>
>                 Key: MRM-798
>                 URL: http://jira.codehaus.org/browse/MRM-798
>             Project: Archiva
>          Issue Type: Improvement
>          Components: repository interface
>    Affects Versions: 1.0.2
>            Reporter: Marc Lustig
>            Assignee: Brett Porter
>             Fix For: 1.2
>
>
> once one of the repos configured as a proxy-connector is down, the mvn build-process slows down extremely as the connect time-out is about 1 minute (for each repo and each artifact).
> There should be a configuration available to adjust blacklisting repos that have been identified as non-reachable.
> Such repos should be able to get re-avtivated manually.

-- 
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