Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.1.1
-
Fix Version/s: 1.4-M1
-
Component/s: None
-
Labels:None
-
Environment:MS Windows Server 2003 Standard Edition, SP2
Java 1.6.0_02
Description
Our Archiva instance has trouble connecting to another internal repository. I've confirmed via packet sniffing that the HTTP request is going to our proxy server even though I've configured this particular remote repository to use a direct connection. Archiva works correctly for an undetermined time (last time it was 3 days) and then will suddenly and consistently exhibit the above symptoms. The exception that is logged is below. After Archiva is restarted the symptom will go away for a period of time and reappear. The reappearance is unfortunately unpredictable at this time.
2008-08-13 12:07:28,141 [btpool0-3] WARN org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer error from repository "wdig.releases" for artifact com.go.trove:trove:1.7.4::pom, continuing to next repository. Error message: Download failure on resource http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/trove/trove/1.7.4/trove-1.7.4.pom:Error transferring file (cause: java.io.IOException: Server returned HTTP response code: 500 for URL: http://maven2.corp.dig.com:8080/archiva/repository/internal/com/go/trove/trove/1.7.4/trove-1.7.4.pom)
2008-08-13 12:07:28,156 [btpool0-3] ERROR org.apache.maven.archiva.webdav.ArchivaDavResourceFactory - Failures occurred downloading from some remote repositories:
wdig.releases: Download failure on resource http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/trove/trove/1.7.4/trove-1.7.4.pom:Error transferring file (cause: java.io.IOException: Server returned HTTP response code: 500 for URL: http://maven2.corp.dig.com:8080/archiva/repository/internal/com/go/trove/trove/1.7.4/trove-1.7.4.pom)
org.apache.maven.archiva.policies.ProxyDownloadException: Failures occurred downloading from some remote repositories:
wdig.releases: Download failure on resource http://maven2.corp.dig.com:8080/archiva/repository/internal//com/go/trove/trove/1.7.4/trove-1.7.4.pom:Error transferring file (cause: java.io.IOException: Server returned HTTP response code: 500 for URL: http://maven2.corp.dig.com:8080/archiva/repository/internal/com/go/trove/trove/1.7.4/trove-1.7.4.pom)
at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:191)
at org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.fetchContentFromProxies(ArchivaDavResourceFactory.java:519)
at org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.doGet(ArchivaDavResourceFactory.java:423)
at org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.createResource(ArchivaDavResourceFactory.java:251)
at org.apache.maven.archiva.webdav.RepositoryServlet.service(RepositoryServlet.java:117)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:722)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:404)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:828)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
I think you can also enable the debug in Archiva to verify whether the download went through the proxy. You can do this by setting the log level to DEBUG in WEB-INF/classes/log4j.xml..