Are you able to build from source? I've just checked in some additional logging for proxying failures.
The tarball above will be updated within an hour or so otherwise. Cheers, Brett 2008/7/30 Mark Johnson <[EMAIL PROTECTED]>: > When the app starts, it identifies itself as Archiva 1.2-SNAPSHOT > > The wrapper.conf file in the conf directory displayed a number of > differences when I diffed the files. On closer inspection, there was only > one actual difference, the rest was due to reordering of lines. I don't see > this file in the file system, so it may not matter. > 1.1 referenced: archiva-jetty-1.1.pom > 1.2 referenced: archiva-jetty-1.2-SNAPSHOT.pom > > I am running on RedHat linux, using java 1.5.0_15. > ARCHIVA_BASE=/var/archiva > ARCHIVA_HOME=/opt/apache-archiva > (/opt/apache-archiva is a link: apache-archiva -> > apache-archiva-1.2-SNAPSHOT) > I am executing "/opt/apache-archiva/bin/archiva start" to start archiva. > > I have doubled checked everything, and must admit, I'm confused. I did not > build this code, but downloaded the tar file referenced in the previous post > by Jeff. > > Thanks, > Mark > > > On Mon, Jul 28, 2008 at 8:07 PM, Brett Porter <[EMAIL PROTECTED]>wrote: > >> 2008/7/29 Mark Johnson <[EMAIL PROTECTED]>: >> > I downloaded the snapshot referenced below, extracted it on my linux >> system, >> > updated the wrapper.conf (the only conf file which appeared to have >> changed) >> > to my runtime conf location, and am still having this problem. Any other >> > ideas? >> >> I'm not sure what you mean by this - wrapper.conf shouldn't have >> changed from 1.1 to this, but the webapp itself will have. If you are >> moving from 1.0.2 then the deployment has a number of other changes as >> detailed in the upgrade instructions. >> >> When you started the app, what version did it report itself to be? >> >> > >> > ERROR: >> > 2008-07-28 14:26:38,633 [btpool0-1] WARN >> > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - >> Transfer >> > error from repository "central" for artifact >> > org.codehaus.plexus:plexus-utils:1.1::pom, continuing to next repository. >> > Error message: Download failure on resource [ >> > >> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom]:Errortransferring<http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D:Errortransferring> >> > file >> > 2008-07-28 14:26:38,658 [btpool0-1] ERROR >> > org.apache.maven.archiva.webdav.ArchivaDavResourceFactory - Failures >> > occurred downloading from some remote repositories: >> > central: Download failure on resource [ >> > >> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom]:Errortransferring<http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D:Errortransferring> >> > file org.apache.maven.archiva.policies.ProxyDownloadException: >> > Failures occurred downloading from some remote repositories: >> > central: Download failure on resource [ >> > >> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom]:Errortransferring<http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D:Errortransferring> >> > file >> > 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) >> > >> > On Mon, Jul 28, 2008 at 8:06 AM, Jeffery, Mark <[EMAIL PROTECTED]> >> wrote: >> > >> >> This build >> >> >> >> >> http://vmbuild.apache.org/continuum/workingCopy.action?projectId=652&use >> >> rDirectory=target< >> http://vmbuild.apache.org/continuum/workingCopy.action?projectId=652&userDirectory=target >> > >> >> >> >> resolves the issue. >> >> >> >> Thanks >> >> Jeff >> >> >> >> -----Original Message----- >> >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> >> Sent: 28 July 2008 15:16 >> >> To: [email protected] >> >> Subject: Re: Upgrade from 1.0 to 1.1 : network problem >> >> >> >> Perhaps you could try building from source, or the following build: >> >> >> >> >> http://vmbuild.apache.org/continuum/workingCopy.action?projectId=652&use >> >> rDirectory=target< >> http://vmbuild.apache.org/continuum/workingCopy.action?projectId=652&userDirectory=target >> > >> >> >> >> Cheers, >> >> Brett >> >> >> >> 2008/7/28 Jeffery, Mark <[EMAIL PROTECTED]>: >> >> > I tried replacing the wagon provider api jar. >> >> > >> >> > Still get >> >> > >> >> > Failures occurred downloading from some remote repositories >> >> > Download failure on resource [xxxxxxxxxxxxxxxxxxxxxxxxxxx]:Error >> >> > transferring file >> >> > >> >> > Thanks >> >> > >> >> > Jeff >> >> > >> >> > -----Original Message----- >> >> > From: Brett Porter [mailto:[EMAIL PROTECTED] >> >> > Sent: 28 July 2008 14:14 >> >> > To: [email protected] >> >> > Subject: Re: Upgrade from 1.0 to 1.1 : network problem >> >> > >> >> > The source code is here: >> >> > http://svn.apache.org/repos/asf/archiva/trunk/ >> >> > >> >> > I believe it is also sufficient to replace the wagon-provider-api JAR >> >> > in the 1.1 webapp with: >> >> > >> >> >> http://people.apache.org/~brett/staged-releases-wagon/org/apache/maven/w<http://people.apache.org/%7Ebrett/staged-releases-wagon/org/apache/maven/w> >> < >> http://people.apache.org/%7Ebrett/staged-releases-wagon/org/apache/maven/w >> > >> >> > agon/wagon-provider-api/1.0-beta-4/wagon-provider-api-1.0-beta-4.jar >> >> > >> >> > Cheers, >> >> > Brett >> >> > >> >> > 2008/7/28 Dan Dare <[EMAIL PROTECTED]>: >> >> >> >> >> >> If the problem has been fixed (indicated in JIRA) how do I get hold >> >> of >> >> > the >> >> >> changes that were necessary for the fix ? Source code or SNAP-SHOT is >> >> > fine >> >> >> >> >> >> >> >> >> Brett Porter wrote: >> >> >>> >> >> >>> If you need a network proxy to access central from your repository >> >> >>> server, unfortunately you'll need to use 1.0.2 or wait for a fix to >> >> >>> the issue below (which we're working on this weekend). >> >> >>> >> >> >>> Cheers, >> >> >>> Brett >> >> >>> >> >> >>> 2008/7/26 Mark Johnson <[EMAIL PROTECTED]>: >> >> >>>> Regarding this problem "network proxy fails after upgrading to >> >> > archiva >> >> >>>> 1.1" >> >> >>>> (http://jira.codehaus.org/browse/MRM-884); I am new to Archiva, >> and >> >> > just >> >> >>>> finished getting 1.0.2 running. I decided to convert to 1.1 before >> >> > going >> >> >>>> live, but have hit this problem. My Archiva repositories are >> >> > currently >> >> >>>> empty. If my plan is to point maven to an Archiva internal >> >> > repository, >> >> >>>> and >> >> >>>> proxy to the central repository, and control what is downloaded >> >> from >> >> > the >> >> >>>> central repository with white-lists, does this mean I cannot use >> >> > 1.1? >> >> >>>> Are >> >> >>>> my options to roll back to 1.0.2, or to go directly to the central >> >> >>>> repository (bypass Archiva), then to upload all these items into my >> >> >>>> internal >> >> >>>> repository from my local repository, so that Archiva does not have >> >> > to >> >> >>>> download anything? (I hope that makes sense). >> >> >>>> >> >> >>>> This may seem obvious, but I'm still trying to understand the >> >> >>>> maven/archiva, >> >> >>>> internal/external/proxy repository relationship. I may have gone >> >> as >> >> > far >> >> >>>> as >> >> >>>> I can do without either changing my methodology or my version. >> >> >>>> >> >> >>>> Thanks, >> >> >>>> Mark >> >> >>>> >> >> >>>> >> >> >>>> On Wed, 23 Jul 2008 09:36:04 GMT, djeanprost >> >> > <[EMAIL PROTECTED]> >> >> >>>> wrote >> >> >>>>> I raised a bug. http://jira.codehaus.org/browse/MRM-884. Wait and >> >> > see. >> >> >>>>> >> >> >>>>> >> >> >>>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> -- >> >> >>> Brett Porter >> >> >>> Blog: http://blogs.exist.com/bporter/ >> >> >>> >> >> >>> >> >> >> >> >> >> -- >> >> >> View this message in context: >> >> > >> >> >> http://www.nabble.com/Upgrade-from-1.0-to-1.1-%3A-network-problem-tp1858 >> >> > 7462p18688926.html >> >> >> Sent from the archiva-users mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> > >> >> > >> >> > >> >> > -- >> >> > Brett Porter >> >> > Blog: http://blogs.exist.com/bporter/ >> >> > To read FirstRand Bank's Disclaimer for this email click on the >> >> following address or copy into your Internet browser: >> >> > https://www.fnb.co.za/disclaimer.html >> >> > >> >> > If you are unable to access the Disclaimer, send a blank e-mail to >> >> > [EMAIL PROTECTED] and we will send you a copy of the >> >> Disclaimer. >> >> > >> >> >> >> >> >> >> >> -- >> >> Brett Porter >> >> Blog: http://blogs.exist.com/bporter/ >> >> To read FirstRand Bank's Disclaimer for this email click on the >> following >> >> address or copy into your Internet browser: >> >> https://www.fnb.co.za/disclaimer.html >> >> >> >> If you are unable to access the Disclaimer, send a blank e-mail to >> >> [EMAIL PROTECTED] and we will send you a copy of the >> >> Disclaimer. >> >> >> > >> >> >> >> -- >> Brett Porter >> Blog: http://blogs.exist.com/bporter/ >> > -- Brett Porter Blog: http://blogs.exist.com/bporter/
