Hi,

We have archiva set up as a mirror for remote repositories, using a network 
proxy (because we are behind a corporate firewall). This seems to work when 
building projects and browsing the repositories, but I've noticed that 
Archiva's UI is really slow.

For example, when viewing the Repositories page, the 'Remote Check' column sits 
spinning and in the logs there are several errors:

2014-10-01 15:12:09,516 [http-8080-1] INFO  
org.apache.archiva.rest.services.DefaultRemoteRepositoriesService [] - 
TransferFailedException :Could not read response body.
2014-10-01 15:12:10,032 [http-8080-3] INFO  
org.apache.archiva.rest.services.DefaultRemoteRepositoriesService [] - 
TransferFailedException :Could not read response body.
2014-10-01 15:12:10,032 [http-8080-2] INFO  
org.apache.archiva.rest.services.DefaultRemoteRepositoriesService [] - 
TransferFailedException :Could not read response body.
2014-10-01 15:12:10,667 [http-8080-5] INFO  
org.apache.archiva.rest.services.DefaultRemoteRepositoriesService [] - 
TransferFailedException :Could not read response body.
2014-10-01 15:14:10,051 [http-8080-4] INFO  
org.apache.archiva.rest.services.DefaultRemoteRepositoriesService [] - 
TransferFailedException :Could not read response body.

It appears that this page doesn't use the proxy configuration from the proxy 
connector.

Is there a way to tell Archiva to use the network proxy when checking the 
status of these repositories?

Thanks,
Jamie

Jamie Cavanaugh

Technical Lead  |  Datacom Systems (Wellington) Ltd  |  68-86 Jervois Quay, 
Wellington 6011, New Zealand
[email protected]<mailto:[email protected]>   |  Ph: 
+64 4 460 1527  |  Fax: +64 4 460 1511  |  Mob: +64 27 298 5043
www.datacom.co.nz<http://www.datacom.co.nz/>  |  PO Box 6376, Wellington 6140

Winner of Hi-Tech New Zealand Company of the Year Award 2010
Finalist for Hi-Tech New Zealand Company of the Decade Award 2011

Reply via email to