Archiva

Archiva is very slow when remote repository is unreachable

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 1.0.2
  • Fix Version/s: 1.4
  • Component/s: remote proxy
  • Labels:
    None
  • Environment:
    Debian
  • Number of attachments :
    0

Description

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.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MRM-1067 Archiva fails to properly deal with overloaded upstream proxy

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Task - A task that needs to be done. MRM-1347 Migrate repository proxy to the new repository API

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.
relates to

Improvement - An improvement or enhancement to an existing feature or task. MRM-798 blacklisting unavailable remote reps

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
James William Dumay added a comment -

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.

Show
James William Dumay added a comment - 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.
Hide
Permalink
James William Dumay added a comment -

Moving this off to 1.3 for the merge of the new repo api

Show
James William Dumay added a comment - Moving this off to 1.3 for the merge of the new repo api
Hide
Permalink
Brett Porter added a comment -

refer to thread dump in linked issue for additional information

Show
Brett Porter added a comment - refer to thread dump in linked issue for additional information
Hide
Permalink
Stephen Spencer added a comment -

Just to note that we got hit by this issue this morning as Adobe's svn and repo is timing out.
It's an especially unpleasant bug because no errors are thrown, and the web admin still works quickly, it just makes Archiva take a very very long time when serving any artifact, even non-snapshot ones where I would assume proxy connections would not even be used.

Show
Stephen Spencer added a comment - Just to note that we got hit by this issue this morning as Adobe's svn and repo is timing out. It's an especially unpleasant bug because no errors are thrown, and the web admin still works quickly, it just makes Archiva take a very very long time when serving any artifact, even non-snapshot ones where I would assume proxy connections would not even be used.

People

  • Assignee:
    James William Dumay
    Reporter:
    Thilo Tanner
Vote (1)
Watch (4)

Dates

  • Created:
    Updated: