RE: Proxy connectors fails to download, Archiva needs restart
Also, if the artifact is in the local cache and this failure happens, shouldn't is simply log it and then return the cached artifact? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2008 6:29 AM To: archiva-users@maven.apache.org Subject: Re: Proxy connectors fails to download, Archiva needs restart ok, it looks like maybe they've blocked you in some way. Archiva 1.0.2 should improve on the reporting of this, and allows the error handling to be configurable. - Brett On 04/04/2008, Jackson, Brian R [EMAIL PROTECTED] wrote: That didn't take long. Here's the full stacktrace, which implies that the remote repository is returning a 500 error, but if I hit the same URL through a browser I can't reproduce the 500 error. I will coordinate with the owner of the remote repository and see if I can get more info from the logs on his end. 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Path [com/go/tea/tea/3.3.11/tea-3.3.11.pom] is part of blacklist (skipping transfer from repository [Central Repository]). 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [cache-failures] policy with [no] 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures - OK to fetch, check-failures policy set to NO. 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [releases] policy with [once] 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:releases - OK to update releases, local file does not exist. 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [snapshots] policy with [never] 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:snapshots - OK to update, snapshot policy does not apply for non-snapshot versions. 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - No authentication for remote repository needed 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Retrieving com/go/tea/tea/3.3.11/tea-3.3.11.pom from WDIG Releases 419035 [SocketListener0-1] WARN org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Transfer error from repository wdig.releases for artifact com.go.tea:tea:3.3.11::pom, continuing to next repository. Error message: Download failure on resource [http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/tea /tea/3.3.11/tea-3.3.11.pom]:Error transferring file 419035 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Full stack trace org.apache.maven.archiva.proxy.ProxyException: Download failure on resource [http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/tea /tea/3.3.11/tea-3.3.11.pom]:Error transferring file at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transfer SimpleFile(DefaultRepositoryProxyConnectors.java:717) at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transfer File(DefaultRepositoryProxyConnectors.java:542) at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFro mProxies(DefaultRepositoryProxyConnectors.java:155) at org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSide Relocation(ProxiedDavServer.java:447) at org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFro mProxies(ProxiedDavServer.java:354) at org.apache.maven.archiva.web.repository.ProxiedDavServer.process(Proxied DavServer.java:189) at org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet. service(MultiplexedWebDavServlet.java:119) at org.apache.maven.archiva.web.repository.RepositoryServlet.service(Reposi toryServlet.java:155) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web ApplicationHandler.java:830) at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDisp atcher.java:189) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web ApplicationHandler.java:821) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.j ava:39) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web ApplicationHandler.java:821) at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(Action ContextCleanUp.java:88
RE: Proxy connectors fails to download, Archiva needs restart
It does just that. The problem I'm having is with artifacts that haven't been cached yet. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] .org] On Behalf Of Jason Chaffee Sent: Thursday, April 03, 2008 2:44 PM To: archiva-users@maven.apache.org Subject: RE: Proxy connectors fails to download, Archiva needs restart Also, if the artifact is in the local cache and this failure happens, shouldn't is simply log it and then return the cached artifact? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2008 6:29 AM To: archiva-users@maven.apache.org Subject: Re: Proxy connectors fails to download, Archiva needs restart ok, it looks like maybe they've blocked you in some way. Archiva 1.0.2 should improve on the reporting of this, and allows the error handling to be configurable. - Brett On 04/04/2008, Jackson, Brian R [EMAIL PROTECTED] wrote: That didn't take long. Here's the full stacktrace, which implies that the remote repository is returning a 500 error, but if I hit the same URL through a browser I can't reproduce the 500 error. I will coordinate with the owner of the remote repository and see if I can get more info from the logs on his end. 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Path [com/go/tea/tea/3.3.11/tea-3.3.11.pom] is part of blacklist (skipping transfer from repository [Central Repository]). 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [cache-failures] policy with [no] 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures - OK to fetch, check-failures policy set to NO. 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [releases] policy with [once] 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:releases - OK to update releases, local file does not exist. 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [snapshots] policy with [never] 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:snapshots - OK to update, snapshot policy does not apply for non-snapshot versions. 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - No authentication for remote repository needed 418722 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Retrieving com/go/tea/tea/3.3.11/tea-3.3.11.pom from WDIG Releases 419035 [SocketListener0-1] WARN org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Transfer error from repository wdig.releases for artifact com.go.tea:tea:3.3.11::pom, continuing to next repository. Error message: Download failure on resource [http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/tea /tea/3.3.11/tea-3.3.11.pom]:Error transferring file 419035 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Full stack trace org.apache.maven.archiva.proxy.ProxyException: Download failure on resource [http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/tea /tea/3.3.11/tea-3.3.11.pom]:Error transferring file at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transfer SimpleFile(DefaultRepositoryProxyConnectors.java:717) at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transfer File(DefaultRepositoryProxyConnectors.java:542) at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFro mProxies(DefaultRepositoryProxyConnectors.java:155) at org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSide Relocation(ProxiedDavServer.java:447) at org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFro mProxies(ProxiedDavServer.java:354) at org.apache.maven.archiva.web.repository.ProxiedDavServer.process(Proxied DavServer.java:189) at org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet. service(MultiplexedWebDavServlet.java:119) at org.apache.maven.archiva.web.repository.RepositoryServlet.service(Reposi toryServlet.java:155) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web ApplicationHandler.java:830) at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDisp atcher.java:189) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web ApplicationHandler.java:821
Re: Proxy connectors fails to download, Archiva needs restart
This was reported by others against 1.0.1, and they've been unable to reproduce with 1.0.2. That release is currently being voted on - you can test it out from here: http://people.apache.org/builds/maven/archiva/1.0.2/ - Brett On 04/04/2008, Jackson, Brian R [EMAIL PROTECTED] wrote: I sniffed the traffic and it's attempting to connect through the network proxy I've setup for some of my other Proxy Connectors. I've double-checked that the Proxy Connector for wdig.releases, the remote repo that is failing, is configured to (direct connection). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] .org] On Behalf Of Jackson, Brian R Sent: Thursday, April 03, 2008 11:36 AM To: archiva-users@maven.apache.org Subject: RE: Proxy connectors fails to download, Archiva needs restart I spoke with Joe, the owner of the remote repository, and we tested it. Apparently the request is not getting to the remote repository as the archiva.log, audit.log and wrapper.log on that server showed no activity at all while mine reports the exception caused by the 500 error. I will now follow up with our MIS and operations team to trace the request as see where it is being blocked. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] .org] On Behalf Of Brett Porter Sent: Thursday, April 03, 2008 9:52 AM To: archiva-users@maven.apache.org Subject: Re: Proxy connectors fails to download, Archiva needs restart On 04/04/2008, Jackson, Brian R [EMAIL PROTECTED] wrote: Why would restarting MY instance of Archiva temporarily fix this issue though? I'll get more information from the remote side when the owner is available. Good point - sorry I forgot that. Let's see what they have to say - though others have also reported this so perhaps there is something else going on here. Thanks, Brett -- Brett Porter Blog: http://blogs.exist.com/bporter/ -- Brett Porter Blog: http://blogs.exist.com/bporter/
RE: Proxy connectors fails to download, Archiva needs restart
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/
