FYI, I have noticed something similar after Archiva is up for a while and I thought it was related to my other consumer issues so I didn't mention it. One possibility to consider is the difference of Archiva being used as both a proxy and repository manager as opposed to just a proxy.
Anyway, I thought I should let it be know that others are seeing this behavior as well. -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2008 3:10 PM To: archiva-users@maven.apache.org Subject: Re: Proxy connectors fails to download, Archiva needs restart I commented in the JIRA issue - it'd be great if you could turn on debug level logging in log4j.xml to see what the exception is that causes this. Cheers, Brett On 03/04/2008, Jackson, Brian R <[EMAIL PROTECTED]> wrote: > I'm experiencing the following issue. After the Archiva server has been > up for some time, one of my proxy connectors starts to fail and the only > solution is to restart the service. I see the following errors in the > log: > > > > 76814726 [SocketListener0-0] WARN > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - > Transfer error from repository "wdig.releases" for artifact > com.go.trove:trove:1.5.4::pom, continuing to next repository. Error > message: Download failure on resource > > > > > > The repository wdig.releases is another Archiva instance that we have > internal to our company. The proxy connector is setup for a direct > connection with no HTTP proxying. I know the network connection isn't > an issue because a restart of just the Archiva service solves the > problem temporarily. > > > > _______________________________________ > > Brian Jackson > > Sr. Software Engineer > > ESPN.com Fantasy Games > > (860) 766-2511 > > > > -- Brett Porter Blog: http://blogs.exist.com/bporter/