No luck. Now I'm getting the following exception in my wrapper.log. I sniffed the traffic and its still trying to connect through our HTTP proxy even though I configured it to connect directly.
INFO | jvm 1 | 2008/04/04 15:34:02 | WARNING: /archiva/repository/releases/com/go/trove/trove/1.7.1/trove-1.7.1.jar: INFO | jvm 1 | 2008/04/04 15:34:02 | org.apache.maven.archiva.policies.ProxyDownloadException: Failures occurred downloading from some remote repositories: INFO | jvm 1 | 2008/04/04 15:34:02 | wdig.releases: Download failure on resource [http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/tro ve/trove/1.7.1/trove-1.7.1.pom]:Error transferring file INFO | jvm 1 | 2008/04/04 15:34:02 | at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFro mProxies(DefaultRepositoryProxyConnectors.java:197) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSide Relocation(ProxiedDavServer.java:438) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFro mProxies(ProxiedDavServer.java:353) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.apache.maven.archiva.web.repository.ProxiedDavServer.process(Proxied DavServer.java:188) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet. service(MultiplexedWebDavServlet.java:119) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.apache.maven.archiva.web.repository.RepositoryServlet.service(Reposi toryServlet.java:155) INFO | jvm 1 | 2008/04/04 15:34:02 | at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web ApplicationHandler.java:830) INFO | jvm 1 | 2008/04/04 15:34:02 | at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDisp atcher.java:189) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web ApplicationHandler.java:821) INFO | jvm 1 | 2008/04/04 15:34:02 | at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.j ava:39) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web ApplicationHandler.java:821) INFO | jvm 1 | 2008/04/04 15:34:02 | at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(Action ContextCleanUp.java:88) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web ApplicationHandler.java:821) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationH andler.java:471) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationCon text.java:633) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.http.HttpServer.service(HttpServer.java:909) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244 ) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) INFO | jvm 1 | 2008/04/04 15:34:02 | at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] .org] On Behalf Of Jackson, Brian R Sent: Friday, April 04, 2008 10:25 AM To: archiva-users@maven.apache.org Subject: RE: Proxy connectors fails to download, Archiva needs restart Excellent! I'll try it out and let you know if it happens again. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] .org] On Behalf Of Brett Porter Sent: Thursday, April 03, 2008 6:48 PM To: archiva-users@maven.apache.org Subject: 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/
