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

Posted to issues@archiva.apache.org by "James William Dumay (JIRA)" <ji...@codehaus.org> on 2008/06/11 04:07:12 UTC

[jira] Updated: (MRM-830) Archiva is very slow when remote repository is unreachable

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

James William Dumay updated MRM-830:
------------------------------------

    Fix Version/s: 1.2

We should look at this after 1.1 (and possibly back port it to the 1.1.x branch).

I'm under the opinion that all calls to remote repositories should be asynchronous and that Archiva should serve the data that becomes available first. This will most likely also boost proxy performance.

> Archiva is very slow when remote repository is unreachable
> ----------------------------------------------------------
>
>                 Key: MRM-830
>                 URL: http://jira.codehaus.org/browse/MRM-830
>             Project: Archiva
>          Issue Type: Bug
>          Components: remote proxy
>    Affects Versions: 1.0.2
>         Environment: Debian
>            Reporter: Thilo Tanner
>            Priority: Critical
>             Fix For: 1.2
>
>
> If a remote repository is not available (e.g. network error) then ALL artifact downloads (even from different remote repos) from clients are very slow. If the remote repo is removed from the config everything works again.

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