Re: Repository timeouts.

[Brett Porter <br...@apache.org>]

Is the timeout not working, or is the 2 seconds still too long?

What you've done is probably correct for now. In Archiva 1.2, there is  
a "take remote repository offline" setting that you could use instead  
that makes what you've done easier. You might consider upgrading - it  
should be straightforward.

- Brett

On 21/08/2009, at 4:35 PM, Michael Delaney wrote:

> All,
>
> Over the last week, or two, we've been plagued with remote  
> repositories that we proxy going down and causing build times to  
> balloon to an unacceptable mount. We've tried setting up some white/ 
> black lists and even setting the time out for our remote  
> repositories to very small values (between two and five seconds). In  
> the end, we usually have to remove those remote repositories from  
> the Archiva settings file then add them back when they(the remote  
> repositories) are responsive again.
>
> What is the best way to deal with this? We're using Archiva 1.1.3 on  
> Solaris.

Re: Repository timeouts.

[Michael Delaney <md...@upromise.com>]

Brett,

Setting the timeout to two seconds add a few minutes to the build time, 
which we're trying to avoid. From what we can tell the timeout is 
working just fine.

Brett Porter wrote:
> Is the timeout not working, or is the 2 seconds still too long?
>
> What you've done is probably correct for now. In Archiva 1.2, there is 
> a "take remote repository offline" setting that you could use instead 
> that makes what you've done easier. You might consider upgrading - it 
> should be straightforward.
>
> - Brett
>
> On 21/08/2009, at 4:35 PM, Michael Delaney wrote:
>
>> All,
>>
>> Over the last week, or two, we've been plagued with remote 
>> repositories that we proxy going down and causing build times to 
>> balloon to an unacceptable mount. We've tried setting up some 
>> white/black lists and even setting the time out for our remote 
>> repositories to very small values (between two and five seconds). In 
>> the end, we usually have to remove those remote repositories from the 
>> Archiva settings file then add them back when they(the remote 
>> repositories) are responsive again.
>>
>> What is the best way to deal with this? We're using Archiva 1.1.3 on 
>> Solaris.
>