You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by djeanprost <dj...@sofaxis.com> on 2008/07/22 15:13:12 UTC
Upgrade from 1.0 to 1.1 : network problem
Hello,
I'm trying to upgrade from 1.0 to 1.1. I use a network proxy to access
remote repos. When using 1.0, I get no error, and when using 1.1, I get this
error.
I double checked my configuration, and there is no differences between my
1.0's config and my 1.1's config.
Did someone met the same problem ?
regards,
dom
2008-07-22 15:02:40,099 [btpool0-7] DEBUG
org.apache.maven.archiva.policies.AbstractUpdatePolicy - OK to update,
snapshot policy does not apply for non-snapshot versions.
2008-07-22 15:02:40,099 [btpool0-7] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - No
authentication for remote repository needed
2008-07-22 15:02:40,114 [btpool0-7] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
Retrieving
org/apache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0-beta-6.pom
from Central Repository
2008-07-22 15:02:57,395 [btpool0-7] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[propagate-errors-on-update] policy with [artifact not already present]
2008-07-22 15:02:57,395 [btpool0-7] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[propagate-errors] policy with [queue error]
2008-07-22 15:02:57,395 [btpool0-7] WARN
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
error from repository "central" for artifact
org.apache.maven.plugins:maven-site-plugin:2.0-beta-6::pom, continuing to
next repository. Error message: Download failure on resource
[http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0-beta-6.pom]:Error
transferring file
2008-07-22 15:02:57,410 [btpool0-7] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Full
stack trace
org.apache.maven.archiva.proxy.ProxyException: Download failure on resource
[http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0-beta-6.pom]:Error
transferring file
at
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferSimpleFile(DefaultRepositoryProxyConnectors.java:747)
at
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferFile(DefaultRepositoryProxyConnectors.java:564)
at
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:171)
at
org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.fetchContentFromProxies(ArchivaDavResourceFactory.java:520)
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:119)
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)
Caused by: org.apache.maven.wagon.TransferFailedException: Error
transferring file
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:136)
at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferSimpleFile(DefaultRepositoryProxyConnectors.java:704)
... 31 more
Caused by: java.net.UnknownHostException: repo1.maven.org
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown
Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
Source)
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:115)
... 35 more
--
View this message in context: http://www.nabble.com/Upgrade-from-1.0-to-1.1-%3A-network-problem-tp18587462p18587462.html
Sent from the archiva-users mailing list archive at Nabble.com.
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by djeanprost <dj...@sofaxis.com>.
I raised a bug. http://jira.codehaus.org/browse/MRM-884. Wait and see.
xelua42 wrote:
>
> Hi,
>
> I have the same problem after my upgrade from 1.0.2 to 1.1 and I don't
> find a solution.
>
> Best regards
> Stéphane
>
>
--
View this message in context: http://www.nabble.com/Upgrade-from-1.0-to-1.1-%3A-network-problem-tp18587462p18607112.html
Sent from the archiva-users mailing list archive at Nabble.com.
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by xelua42 <xe...@gmail.com>.
Hi,
I have the same problem after my upgrade from 1.0.2 to 1.1 and I don't
find a solution.
Best regards
Stéphane
djeanprost wrote:
>
> Hello,
>
> I'm trying to upgrade from 1.0 to 1.1. I use a network proxy to access
> remote repos. When using 1.0, I get no error, and when using 1.1, I get
> this error.
> I double checked my configuration, and there is no differences between my
> 1.0's config and my 1.1's config.
> Did someone met the same problem ?
> regards,
> dom
>
>
> 2008-07-22 15:02:40,099 [btpool0-7] DEBUG
> org.apache.maven.archiva.policies.AbstractUpdatePolicy - OK to update,
> snapshot policy does not apply for non-snapshot versions.
> 2008-07-22 15:02:40,099 [btpool0-7] DEBUG
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - No
> authentication for remote repository needed
> 2008-07-22 15:02:40,114 [btpool0-7] DEBUG
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Retrieving
> org/apache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0-beta-6.pom
> from Central Repository
> 2008-07-22 15:02:57,395 [btpool0-7] DEBUG
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Applying [propagate-errors-on-update] policy with [artifact not already
> present]
> 2008-07-22 15:02:57,395 [btpool0-7] DEBUG
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Applying [propagate-errors] policy with [queue error]
> 2008-07-22 15:02:57,395 [btpool0-7] WARN
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Transfer error from repository "central" for artifact
> org.apache.maven.plugins:maven-site-plugin:2.0-beta-6::pom, continuing to
> next repository. Error message: Download failure on resource
> [http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0-beta-6.pom]:Error
> transferring file
> 2008-07-22 15:02:57,410 [btpool0-7] DEBUG
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Full
> stack trace
> org.apache.maven.archiva.proxy.ProxyException: Download failure on
> resource
> [http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0-beta-6.pom]:Error
> transferring file
> at
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferSimpleFile(DefaultRepositoryProxyConnectors.java:747)
> at
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferFile(DefaultRepositoryProxyConnectors.java:564)
> at
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:171)
> at
> org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.fetchContentFromProxies(ArchivaDavResourceFactory.java:520)
> 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:119)
> 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)
> Caused by: org.apache.maven.wagon.TransferFailedException: Error
> transferring file
> at
> org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:136)
> at
> org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
> at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
> at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
> at
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferSimpleFile(DefaultRepositoryProxyConnectors.java:704)
> ... 31 more
> Caused by: java.net.UnknownHostException: repo1.maven.org
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at sun.net.NetworkClient.doConnect(Unknown Source)
> at sun.net.www.http.HttpClient.openServer(Unknown Source)
> at sun.net.www.http.HttpClient.openServer(Unknown Source)
> at sun.net.www.http.HttpClient.<init>(Unknown Source)
> at sun.net.www.http.HttpClient.New(Unknown Source)
> at sun.net.www.http.HttpClient.New(Unknown Source)
> at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown
> Source)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown
> Source)
> at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
> Source)
> at
> org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:115)
> ... 35 more
>
--
View this message in context: http://www.nabble.com/Upgrade-from-1.0-to-1.1-%3A-network-problem-tp18587462p18606594.html
Sent from the archiva-users mailing list archive at Nabble.com.
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Mark Johnson <am...@gmail.com>.
Problem Solved. After much investigation, I had to create a network proxy.
This worked fine (with on proxy) on my windows server, but not on my Linux
server. One of the great things about a large company where no one person
knows all the necessary information! I suspect that ever since the original
1.2 snapshot that solved the proxy problem, I have been struggling with my
internet access, and the errors are quite similar.
Thanks Brett for your help.
Mark
On Mon, Aug 11, 2008 at 3:23 PM, Mark Johnson <am...@gmail.com>wrote:
> I cannot seem to resolve the proxy download error. I'm wondering if I have
> something configured incorrectly in archiva. Does anyone have any further
> suggestions?
>
> I have started over clean with archiva using 1.1.1. I then pasted the
> "test url" in the instructions (modified for my install), as shown below:
>
> ########### BROWSER TEST AND ERROR ############
>
> http://cvstest.pcl.ingenix.com:8880/archiva/repository/internal/junit/junit/3.8.1/junit-3.8.1.jar
> This resulted in:
> HTTP ERROR: 500
>
> Unable to fetch artifact resource.
>
> RequestURI=/archiva/repository/internal/junit/junit/3.8.1/junit-3.8.1.jar*
> *
> ########### archiva.log output ################
>
> 2008-08-11 15:16:13,636 [btpool0-2] WARN
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
> error from repository "central" for artifact junit:junit:3.8.1::pom,
> continuing to next repository. Error message: Download failure on resource [
> http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom]:Error<http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom%5D%3AError>transferring file (cause: java.net.ConnectException: Connection refused)
> 2008-08-11 15:16:13,637 [btpool0-2] ERROR
> org.apache.maven.archiva.webdav.ArchivaDavResourceFactory - Failures
> occurred downloading from some remote repositories:
> central: Download failure on resource [
> http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom]:Error<http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom%5D%3AError>transferring file (cause: java.net.ConnectException: Connection refused)
> org.apache.maven.archiva.policies.ProxyDownloadException: Failures occurred
> downloading from some remote repositories:
> central: Download failure on resource [
> http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom]:Error<http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom%5D%3AError>transferring file (cause: java.net.ConnectException: Connection refused)
> at
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:191)
> at
> org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.applyServerSideRelocation(ArchivaDavResourceFactory.java:601)
> at
> org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.fetchContentFromProxies(ArchivaDavResourceFactory.java:517)
>
> 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)
>
> Thanks,
> Mark
>
>
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Mark Johnson <am...@gmail.com>.
I cannot seem to resolve the proxy download error. I'm wondering if I have
something configured incorrectly in archiva. Does anyone have any further
suggestions?
I have started over clean with archiva using 1.1.1. I then pasted the "test
url" in the instructions (modified for my install), as shown below:
########### BROWSER TEST AND ERROR ############
http://cvstest.pcl.ingenix.com:8880/archiva/repository/internal/junit/junit/3.8.1/junit-3.8.1.jar
This resulted in:
HTTP ERROR: 500
Unable to fetch artifact resource.
RequestURI=/archiva/repository/internal/junit/junit/3.8.1/junit-3.8.1.jar*
*
########### archiva.log output ################
2008-08-11 15:16:13,636 [btpool0-2] WARN
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
error from repository "central" for artifact junit:junit:3.8.1::pom,
continuing to next repository. Error message: Download failure on resource [
http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom]:Errortransferring
file (cause: java.net.ConnectException: Connection refused)
2008-08-11 15:16:13,637 [btpool0-2] ERROR
org.apache.maven.archiva.webdav.ArchivaDavResourceFactory - Failures
occurred downloading from some remote repositories:
central: Download failure on resource [
http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom]:Errortransferring
file (cause: java.net.ConnectException: Connection refused)
org.apache.maven.archiva.policies.ProxyDownloadException: Failures occurred
downloading from some remote repositories:
central: Download failure on resource [
http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom]:Errortransferring
file (cause: java.net.ConnectException: Connection refused)
at
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:191)
at
org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.applyServerSideRelocation(ArchivaDavResourceFactory.java:601)
at
org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.fetchContentFromProxies(ArchivaDavResourceFactory.java:517)
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)
Thanks,
Mark
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Mark Johnson <am...@gmail.com>.
Here is the error and stack trace with logging turned up. Sorry it took me
a while....my job got in the way.
2008-07-30 10:18:44,534 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[releases] policy with [once]
2008-07-30 10:18:44,534 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[releases] policy with [once]
2008-07-30 10:18:44,535 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[snapshots] policy with [never]
2008-07-30 10:18:44,535 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[snapshots] policy with [never]
2008-07-30 10:18:44,535 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[cache-failures] policy with [no]
2008-07-30 10:18:44,535 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[cache-failures] policy with [no]
2008-07-30 10:18:44,557 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
Retrieving commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom
from Central Repository
2008-07-30 10:18:44,557 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
Retrieving commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom
from Central Repository
2008-07-30 10:18:44,607 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[propagate-errors-on-update] policy with [artifact not already present]
2008-07-30 10:18:44,607 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[propagate-errors-on-update] policy with [artifact not already present]
2008-07-30 10:18:44,608 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[propagate-errors] policy with [queue error]
2008-07-30 10:18:44,608 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Applying
[propagate-errors] policy with [queue error]
2008-07-30 10:18:44,611 [btpool0-8] WARN
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
error from repository "central" for artifact
commons-logging:commons-logging:1.0.4::pom, continuing to next repository.
Error message: Download failure on resource [
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom]:Errortransferring
file (cause: java.net.ConnectException: Connection refused)
2008-07-30 10:18:44,611 [btpool0-8] WARN
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
error from repository "central" for artifact
commons-logging:commons-logging:1.0.4::pom, continuing to next repository.
Error message: Download failure on resource [
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom]:Errortransferring
file (cause: java.net.ConnectException: Connection refused)
2008-07-30 10:18:44,614 [btpool0-8] DEBUG
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Full
stack trace
org.apache.maven.archiva.proxy.ProxyException: Download failure on resource
[
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom]:Errortransferring
file (cause: java.net.ConnectException: Connection refused)
at
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferSimpleFile(DefaultRepositoryProxyConnectors.java:833)
at
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferFile(DefaultRepositoryProxyConnectors.java:611)
at
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:162)
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)
Caused by: org.apache.maven.wagon.TransferFailedException: Error
transferring file
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:136)
at
org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at
org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferSimpleFile(DefaultRepositoryProxyConnectors.java:782)
... 31 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:520)
at java.net.Socket.connect(Socket.java:470)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
at sun.net.www.http.HttpClient.New(HttpClient.java:304)
at sun.net.www.http.HttpClient.New(HttpClient.java:321)
at
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
at
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934)
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:115)
... 35 more
On Wed, Jul 30, 2008 at 9:23 AM, Brett Porter <br...@gmail.com>wrote:
> Yes, to get the newest logging, you'll need to turn on debug mode
> (it'd be too verbose by default).
>
> If you modify log4j.xml and add "org.apache.maven.archiva.proxy" with
> a level of "debug" you should start to see the proxy details used on
> every request.
>
> - Brett
>
> 2008/7/31 Mark Johnson <am...@gmail.com>:
> > No, there are not an earlier "Could not connect to" warning.
> >
> > I installed the latest snapshot bin tar (7/30, 12:33am). I did not
> modify
> > the log4j.xml, did I need to?
> >
> > Here are the wagon jars in WEB-INF/lib. They should be correct since I
> > deleted my old dir, and extracted clean.
> > -rw-r--r-- 1 archiva users 10131 Jul 27 20:20
> wagon-file-1.0-SNAPSHOT.jar
> > -rw-r--r-- 1 archiva users 13956 Jul 27 20:22
> > wagon-http-lightweight-1.0-SNAPSHOT.jar
> > -rw-r--r-- 1 archiva users 19159 Jul 27 20:21
> > wagon-http-shared-1.0-SNAPSHOT.jar
> > -rw-r--r-- 1 archiva users 52133 Jul 27 20:17
> > wagon-provider-api-1.0-SNAPSHOT.jar
> >
> >
> > 2008-07-30 09:03:44,813 [btpool0-2] 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 (cause: java.net.ConnectException: Connection refused)
> > 2008-07-30 09:03:44,828 [btpool0-2] 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 (cause: java.net.ConnectException: Connection
> > refused)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 (cause: java.net.ConnectException: Connection refused)
> >
> >
> > On Wed, Jul 30, 2008 at 12:20 AM, Brett Porter <brett.porter@gmail.com
> >wrote:
> >
> >> 2008/7/30 Brett Porter <br...@gmail.com>:
> >> > Thanks.
> >> >
> >> > Is there any earlier warning "Could not connect to"... ?
> >>
> >> Actually, this might be unlikely. I've checked and the java URL
> >> connection that we're using seems to ignore an invalid proxy rather
> >> than presenting an error.
> >>
> >> I've added some additional code to log the proxy being used on each
> >> request in debug mode (enabled by editing log4j.xml in the web app).
> >>
> >> Can you also check that you have removed all the old wagon-* JARs from
> >> WEB-INF/lib?
> >>
> >> Thanks,
> >> Brett
> >>
> >> >
> >> > Cheers,
> >> > Brett
> >> >
> >> > 2008/7/30 Mark Johnson <am...@gmail.com>:
> >> >> I did not build, but downloaded the new tarball. I have pasted the
> >> message
> >> >> below. The new information appears to be the "Connection Refused"
> >> >> information:
> >> >>
> >> >> 2008-07-29 13:50:29,102 [btpool0-5] WARN
> >> >> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> >> Transfer
> >> >> error from repository "central" for artifact
> >> >> org.apache.maven.surefire:surefire:2.4.2::pom, continuing to next
> >> >> repository. Error message: Download failure on resource [
> >> >>
> >>
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring<http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring>
> <
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring
> >
> >> >> file (cause: java.net.ConnectException: Connection refused)
> >> >> 2008-07-29 13:50:29,119 [btpool0-5] 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/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring<http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring>
> <
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring
> >
> >> >> file (cause: java.net.ConnectException: Connection
> >> >> refused)org.apache.maven.archiva.policies.ProxyDownloadException:
> >> Failures
> >> >> occurred downloading from some remote repositories:
> >> >> central: Download failure on resource [
> >> >>
> >>
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring<http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring>
> <
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring
> >
> >> >> file (cause: java.net.ConnectException: Connection refused)
> >> >>
> >> >>
> >> >> On Tue, Jul 29, 2008 at 11:01 AM, Brett Porter <
> brett.porter@gmail.com
> >> >wrote:
> >> >>
> >> >>> 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 <am...@gmail.com>:
> >> >>> > 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 <
> >> brett.porter@gmail.com
> >> >>> >wrote:
> >> >>> >
> >> >>> >> 2008/7/29 Mark Johnson <am...@gmail.com>:
> >> >>> >> > 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>
> <
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D:Errortransferring
> >
> >> <
> >>
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D: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>
> <
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D:Errortransferring
> >
> >> <
> >>
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D: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>
> <
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D:Errortransferring
> >
> >> <
> >>
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D: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 <
> >> MJeffery@fnb.co.za>
> >> >>> >> 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:brett.porter@gmail.com]
> >> >>> >> >> Sent: 28 July 2008 15:16
> >> >>> >> >> To: users@archiva.apache.org
> >> >>> >> >> 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 <MJ...@fnb.co.za>:
> >> >>> >> >> > 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:brett.porter@gmail.com]
> >> >>> >> >> > Sent: 28 July 2008 14:14
> >> >>> >> >> > To: users@archiva.apache.org
> >> >>> >> >> > 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
> >
> >> <
> >>
> http://people.apache.org/%7Ebrett/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 <da...@gmail.com>:
> >> >>> >> >> >>
> >> >>> >> >> >> 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 <am...@gmail.com>:
> >> >>> >> >> >>>> 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
> >> >>> >> >> > <dj...@sofaxis.com>
> >> >>> >> >> >>>> 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
> >> >>> >> >> > firstrandbankdisclaimer@fnb.co.za 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
> >> >>> >> >> firstrandbankdisclaimer@fnb.co.za 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/
> >> >>>
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Brett Porter
> >> > Blog: http://blogs.exist.com/bporter/
> >> >
> >>
> >>
> >>
> >> --
> >> Brett Porter
> >> Blog: http://blogs.exist.com/bporter/
> >>
> >
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Brett Porter <br...@gmail.com>.
Yes, to get the newest logging, you'll need to turn on debug mode
(it'd be too verbose by default).
If you modify log4j.xml and add "org.apache.maven.archiva.proxy" with
a level of "debug" you should start to see the proxy details used on
every request.
- Brett
2008/7/31 Mark Johnson <am...@gmail.com>:
> No, there are not an earlier "Could not connect to" warning.
>
> I installed the latest snapshot bin tar (7/30, 12:33am). I did not modify
> the log4j.xml, did I need to?
>
> Here are the wagon jars in WEB-INF/lib. They should be correct since I
> deleted my old dir, and extracted clean.
> -rw-r--r-- 1 archiva users 10131 Jul 27 20:20 wagon-file-1.0-SNAPSHOT.jar
> -rw-r--r-- 1 archiva users 13956 Jul 27 20:22
> wagon-http-lightweight-1.0-SNAPSHOT.jar
> -rw-r--r-- 1 archiva users 19159 Jul 27 20:21
> wagon-http-shared-1.0-SNAPSHOT.jar
> -rw-r--r-- 1 archiva users 52133 Jul 27 20:17
> wagon-provider-api-1.0-SNAPSHOT.jar
>
>
> 2008-07-30 09:03:44,813 [btpool0-2] 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
> file (cause: java.net.ConnectException: Connection refused)
> 2008-07-30 09:03:44,828 [btpool0-2] 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
> file (cause: java.net.ConnectException: Connection
> refused)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
> file (cause: java.net.ConnectException: Connection refused)
>
>
> On Wed, Jul 30, 2008 at 12:20 AM, Brett Porter <br...@gmail.com>wrote:
>
>> 2008/7/30 Brett Porter <br...@gmail.com>:
>> > Thanks.
>> >
>> > Is there any earlier warning "Could not connect to"... ?
>>
>> Actually, this might be unlikely. I've checked and the java URL
>> connection that we're using seems to ignore an invalid proxy rather
>> than presenting an error.
>>
>> I've added some additional code to log the proxy being used on each
>> request in debug mode (enabled by editing log4j.xml in the web app).
>>
>> Can you also check that you have removed all the old wagon-* JARs from
>> WEB-INF/lib?
>>
>> Thanks,
>> Brett
>>
>> >
>> > Cheers,
>> > Brett
>> >
>> > 2008/7/30 Mark Johnson <am...@gmail.com>:
>> >> I did not build, but downloaded the new tarball. I have pasted the
>> message
>> >> below. The new information appears to be the "Connection Refused"
>> >> information:
>> >>
>> >> 2008-07-29 13:50:29,102 [btpool0-5] WARN
>> >> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
>> Transfer
>> >> error from repository "central" for artifact
>> >> org.apache.maven.surefire:surefire:2.4.2::pom, continuing to next
>> >> repository. Error message: Download failure on resource [
>> >>
>> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring<http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring>
>> >> file (cause: java.net.ConnectException: Connection refused)
>> >> 2008-07-29 13:50:29,119 [btpool0-5] 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/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring<http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring>
>> >> file (cause: java.net.ConnectException: Connection
>> >> refused)org.apache.maven.archiva.policies.ProxyDownloadException:
>> Failures
>> >> occurred downloading from some remote repositories:
>> >> central: Download failure on resource [
>> >>
>> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring<http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring>
>> >> file (cause: java.net.ConnectException: Connection refused)
>> >>
>> >>
>> >> On Tue, Jul 29, 2008 at 11:01 AM, Brett Porter <brett.porter@gmail.com
>> >wrote:
>> >>
>> >>> 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 <am...@gmail.com>:
>> >>> > 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 <
>> brett.porter@gmail.com
>> >>> >wrote:
>> >>> >
>> >>> >> 2008/7/29 Mark Johnson <am...@gmail.com>:
>> >>> >> > 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>
>> <
>> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D: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>
>> <
>> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D: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>
>> <
>> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D: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 <
>> MJeffery@fnb.co.za>
>> >>> >> 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:brett.porter@gmail.com]
>> >>> >> >> Sent: 28 July 2008 15:16
>> >>> >> >> To: users@archiva.apache.org
>> >>> >> >> 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 <MJ...@fnb.co.za>:
>> >>> >> >> > 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:brett.porter@gmail.com]
>> >>> >> >> > Sent: 28 July 2008 14:14
>> >>> >> >> > To: users@archiva.apache.org
>> >>> >> >> > 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
>> >
>> >>> <
>> >>>
>> 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 <da...@gmail.com>:
>> >>> >> >> >>
>> >>> >> >> >> 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 <am...@gmail.com>:
>> >>> >> >> >>>> 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
>> >>> >> >> > <dj...@sofaxis.com>
>> >>> >> >> >>>> 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
>> >>> >> >> > firstrandbankdisclaimer@fnb.co.za 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
>> >>> >> >> firstrandbankdisclaimer@fnb.co.za 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/
>> >>>
>> >>
>> >
>> >
>> >
>> > --
>> > Brett Porter
>> > Blog: http://blogs.exist.com/bporter/
>> >
>>
>>
>>
>> --
>> Brett Porter
>> Blog: http://blogs.exist.com/bporter/
>>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Mark Johnson <am...@gmail.com>.
No, there are not an earlier "Could not connect to" warning.
I installed the latest snapshot bin tar (7/30, 12:33am). I did not modify
the log4j.xml, did I need to?
Here are the wagon jars in WEB-INF/lib. They should be correct since I
deleted my old dir, and extracted clean.
-rw-r--r-- 1 archiva users 10131 Jul 27 20:20 wagon-file-1.0-SNAPSHOT.jar
-rw-r--r-- 1 archiva users 13956 Jul 27 20:22
wagon-http-lightweight-1.0-SNAPSHOT.jar
-rw-r--r-- 1 archiva users 19159 Jul 27 20:21
wagon-http-shared-1.0-SNAPSHOT.jar
-rw-r--r-- 1 archiva users 52133 Jul 27 20:17
wagon-provider-api-1.0-SNAPSHOT.jar
2008-07-30 09:03:44,813 [btpool0-2] 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
file (cause: java.net.ConnectException: Connection refused)
2008-07-30 09:03:44,828 [btpool0-2] 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
file (cause: java.net.ConnectException: Connection
refused)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
file (cause: java.net.ConnectException: Connection refused)
On Wed, Jul 30, 2008 at 12:20 AM, Brett Porter <br...@gmail.com>wrote:
> 2008/7/30 Brett Porter <br...@gmail.com>:
> > Thanks.
> >
> > Is there any earlier warning "Could not connect to"... ?
>
> Actually, this might be unlikely. I've checked and the java URL
> connection that we're using seems to ignore an invalid proxy rather
> than presenting an error.
>
> I've added some additional code to log the proxy being used on each
> request in debug mode (enabled by editing log4j.xml in the web app).
>
> Can you also check that you have removed all the old wagon-* JARs from
> WEB-INF/lib?
>
> Thanks,
> Brett
>
> >
> > Cheers,
> > Brett
> >
> > 2008/7/30 Mark Johnson <am...@gmail.com>:
> >> I did not build, but downloaded the new tarball. I have pasted the
> message
> >> below. The new information appears to be the "Connection Refused"
> >> information:
> >>
> >> 2008-07-29 13:50:29,102 [btpool0-5] WARN
> >> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Transfer
> >> error from repository "central" for artifact
> >> org.apache.maven.surefire:surefire:2.4.2::pom, continuing to next
> >> repository. Error message: Download failure on resource [
> >>
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring<http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring>
> >> file (cause: java.net.ConnectException: Connection refused)
> >> 2008-07-29 13:50:29,119 [btpool0-5] 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/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring<http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring>
> >> file (cause: java.net.ConnectException: Connection
> >> refused)org.apache.maven.archiva.policies.ProxyDownloadException:
> Failures
> >> occurred downloading from some remote repositories:
> >> central: Download failure on resource [
> >>
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring<http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom%5D:Errortransferring>
> >> file (cause: java.net.ConnectException: Connection refused)
> >>
> >>
> >> On Tue, Jul 29, 2008 at 11:01 AM, Brett Porter <brett.porter@gmail.com
> >wrote:
> >>
> >>> 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 <am...@gmail.com>:
> >>> > 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 <
> brett.porter@gmail.com
> >>> >wrote:
> >>> >
> >>> >> 2008/7/29 Mark Johnson <am...@gmail.com>:
> >>> >> > 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>
> <
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D: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>
> <
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D: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>
> <
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom%5D: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 <
> MJeffery@fnb.co.za>
> >>> >> 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:brett.porter@gmail.com]
> >>> >> >> Sent: 28 July 2008 15:16
> >>> >> >> To: users@archiva.apache.org
> >>> >> >> 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 <MJ...@fnb.co.za>:
> >>> >> >> > 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:brett.porter@gmail.com]
> >>> >> >> > Sent: 28 July 2008 14:14
> >>> >> >> > To: users@archiva.apache.org
> >>> >> >> > 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
> >
> >>> <
> >>>
> 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 <da...@gmail.com>:
> >>> >> >> >>
> >>> >> >> >> 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 <am...@gmail.com>:
> >>> >> >> >>>> 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
> >>> >> >> > <dj...@sofaxis.com>
> >>> >> >> >>>> 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
> >>> >> >> > firstrandbankdisclaimer@fnb.co.za 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
> >>> >> >> firstrandbankdisclaimer@fnb.co.za 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/
> >>>
> >>
> >
> >
> >
> > --
> > Brett Porter
> > Blog: http://blogs.exist.com/bporter/
> >
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Brett Porter <br...@gmail.com>.
2008/7/30 Brett Porter <br...@gmail.com>:
> Thanks.
>
> Is there any earlier warning "Could not connect to"... ?
Actually, this might be unlikely. I've checked and the java URL
connection that we're using seems to ignore an invalid proxy rather
than presenting an error.
I've added some additional code to log the proxy being used on each
request in debug mode (enabled by editing log4j.xml in the web app).
Can you also check that you have removed all the old wagon-* JARs from
WEB-INF/lib?
Thanks,
Brett
>
> Cheers,
> Brett
>
> 2008/7/30 Mark Johnson <am...@gmail.com>:
>> I did not build, but downloaded the new tarball. I have pasted the message
>> below. The new information appears to be the "Connection Refused"
>> information:
>>
>> 2008-07-29 13:50:29,102 [btpool0-5] WARN
>> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
>> error from repository "central" for artifact
>> org.apache.maven.surefire:surefire:2.4.2::pom, continuing to next
>> repository. Error message: Download failure on resource [
>> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring
>> file (cause: java.net.ConnectException: Connection refused)
>> 2008-07-29 13:50:29,119 [btpool0-5] 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/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring
>> file (cause: java.net.ConnectException: Connection
>> refused)org.apache.maven.archiva.policies.ProxyDownloadException: Failures
>> occurred downloading from some remote repositories:
>> central: Download failure on resource [
>> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring
>> file (cause: java.net.ConnectException: Connection refused)
>>
>>
>> On Tue, Jul 29, 2008 at 11:01 AM, Brett Porter <br...@gmail.com>wrote:
>>
>>> 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 <am...@gmail.com>:
>>> > 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 <brett.porter@gmail.com
>>> >wrote:
>>> >
>>> >> 2008/7/29 Mark Johnson <am...@gmail.com>:
>>> >> > 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>
>>> <
>>> 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>
>>> <
>>> 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>
>>> <
>>> 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 <MJ...@fnb.co.za>
>>> >> 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:brett.porter@gmail.com]
>>> >> >> Sent: 28 July 2008 15:16
>>> >> >> To: users@archiva.apache.org
>>> >> >> 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 <MJ...@fnb.co.za>:
>>> >> >> > 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:brett.porter@gmail.com]
>>> >> >> > Sent: 28 July 2008 14:14
>>> >> >> > To: users@archiva.apache.org
>>> >> >> > 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
>>> >
>>> >> <
>>> >>
>>> 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 <da...@gmail.com>:
>>> >> >> >>
>>> >> >> >> 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 <am...@gmail.com>:
>>> >> >> >>>> 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
>>> >> >> > <dj...@sofaxis.com>
>>> >> >> >>>> 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
>>> >> >> > firstrandbankdisclaimer@fnb.co.za 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
>>> >> >> firstrandbankdisclaimer@fnb.co.za 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/
>>>
>>
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Brett Porter <br...@gmail.com>.
Thanks.
Is there any earlier warning "Could not connect to"... ?
Cheers,
Brett
2008/7/30 Mark Johnson <am...@gmail.com>:
> I did not build, but downloaded the new tarball. I have pasted the message
> below. The new information appears to be the "Connection Refused"
> information:
>
> 2008-07-29 13:50:29,102 [btpool0-5] WARN
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
> error from repository "central" for artifact
> org.apache.maven.surefire:surefire:2.4.2::pom, continuing to next
> repository. Error message: Download failure on resource [
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring
> file (cause: java.net.ConnectException: Connection refused)
> 2008-07-29 13:50:29,119 [btpool0-5] 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/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring
> file (cause: java.net.ConnectException: Connection
> refused)org.apache.maven.archiva.policies.ProxyDownloadException: Failures
> occurred downloading from some remote repositories:
> central: Download failure on resource [
> http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring
> file (cause: java.net.ConnectException: Connection refused)
>
>
> On Tue, Jul 29, 2008 at 11:01 AM, Brett Porter <br...@gmail.com>wrote:
>
>> 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 <am...@gmail.com>:
>> > 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 <brett.porter@gmail.com
>> >wrote:
>> >
>> >> 2008/7/29 Mark Johnson <am...@gmail.com>:
>> >> > 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>
>> <
>> 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>
>> <
>> 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>
>> <
>> 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 <MJ...@fnb.co.za>
>> >> 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:brett.porter@gmail.com]
>> >> >> Sent: 28 July 2008 15:16
>> >> >> To: users@archiva.apache.org
>> >> >> 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 <MJ...@fnb.co.za>:
>> >> >> > 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:brett.porter@gmail.com]
>> >> >> > Sent: 28 July 2008 14:14
>> >> >> > To: users@archiva.apache.org
>> >> >> > 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
>> >
>> >> <
>> >>
>> 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 <da...@gmail.com>:
>> >> >> >>
>> >> >> >> 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 <am...@gmail.com>:
>> >> >> >>>> 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
>> >> >> > <dj...@sofaxis.com>
>> >> >> >>>> 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
>> >> >> > firstrandbankdisclaimer@fnb.co.za 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
>> >> >> firstrandbankdisclaimer@fnb.co.za 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/
>>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Mark Johnson <am...@gmail.com>.
I did not build, but downloaded the new tarball. I have pasted the message
below. The new information appears to be the "Connection Refused"
information:
2008-07-29 13:50:29,102 [btpool0-5] WARN
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
error from repository "central" for artifact
org.apache.maven.surefire:surefire:2.4.2::pom, continuing to next
repository. Error message: Download failure on resource [
http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring
file (cause: java.net.ConnectException: Connection refused)
2008-07-29 13:50:29,119 [btpool0-5] 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/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring
file (cause: java.net.ConnectException: Connection
refused)org.apache.maven.archiva.policies.ProxyDownloadException: Failures
occurred downloading from some remote repositories:
central: Download failure on resource [
http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.4.2/surefire-2.4.2.pom]:Errortransferring
file (cause: java.net.ConnectException: Connection refused)
On Tue, Jul 29, 2008 at 11:01 AM, Brett Porter <br...@gmail.com>wrote:
> 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 <am...@gmail.com>:
> > 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 <brett.porter@gmail.com
> >wrote:
> >
> >> 2008/7/29 Mark Johnson <am...@gmail.com>:
> >> > 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>
> <
> 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>
> <
> 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>
> <
> 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 <MJ...@fnb.co.za>
> >> 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:brett.porter@gmail.com]
> >> >> Sent: 28 July 2008 15:16
> >> >> To: users@archiva.apache.org
> >> >> 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 <MJ...@fnb.co.za>:
> >> >> > 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:brett.porter@gmail.com]
> >> >> > Sent: 28 July 2008 14:14
> >> >> > To: users@archiva.apache.org
> >> >> > 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
> >
> >> <
> >>
> 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 <da...@gmail.com>:
> >> >> >>
> >> >> >> 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 <am...@gmail.com>:
> >> >> >>>> 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
> >> >> > <dj...@sofaxis.com>
> >> >> >>>> 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
> >> >> > firstrandbankdisclaimer@fnb.co.za 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
> >> >> firstrandbankdisclaimer@fnb.co.za 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/
>
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Brett Porter <br...@gmail.com>.
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 <am...@gmail.com>:
> 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 <br...@gmail.com>wrote:
>
>> 2008/7/29 Mark Johnson <am...@gmail.com>:
>> > 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 <MJ...@fnb.co.za>
>> 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:brett.porter@gmail.com]
>> >> Sent: 28 July 2008 15:16
>> >> To: users@archiva.apache.org
>> >> 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 <MJ...@fnb.co.za>:
>> >> > 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:brett.porter@gmail.com]
>> >> > Sent: 28 July 2008 14:14
>> >> > To: users@archiva.apache.org
>> >> > 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 <da...@gmail.com>:
>> >> >>
>> >> >> 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 <am...@gmail.com>:
>> >> >>>> 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
>> >> > <dj...@sofaxis.com>
>> >> >>>> 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
>> >> > firstrandbankdisclaimer@fnb.co.za 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
>> >> firstrandbankdisclaimer@fnb.co.za 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/
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Mark Johnson <am...@gmail.com>.
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 <br...@gmail.com>wrote:
> 2008/7/29 Mark Johnson <am...@gmail.com>:
> > 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 <MJ...@fnb.co.za>
> 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:brett.porter@gmail.com]
> >> Sent: 28 July 2008 15:16
> >> To: users@archiva.apache.org
> >> 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 <MJ...@fnb.co.za>:
> >> > 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:brett.porter@gmail.com]
> >> > Sent: 28 July 2008 14:14
> >> > To: users@archiva.apache.org
> >> > 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 <da...@gmail.com>:
> >> >>
> >> >> 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 <am...@gmail.com>:
> >> >>>> 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
> >> > <dj...@sofaxis.com>
> >> >>>> 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
> >> > firstrandbankdisclaimer@fnb.co.za 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
> >> firstrandbankdisclaimer@fnb.co.za and we will send you a copy of the
> >> Disclaimer.
> >>
> >
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Brett Porter <br...@gmail.com>.
2008/7/29 Mark Johnson <am...@gmail.com>:
> 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
> 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
> 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
> 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 <MJ...@fnb.co.za> 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:brett.porter@gmail.com]
>> Sent: 28 July 2008 15:16
>> To: users@archiva.apache.org
>> 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 <MJ...@fnb.co.za>:
>> > 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:brett.porter@gmail.com]
>> > Sent: 28 July 2008 14:14
>> > To: users@archiva.apache.org
>> > 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>
>> > agon/wagon-provider-api/1.0-beta-4/wagon-provider-api-1.0-beta-4.jar
>> >
>> > Cheers,
>> > Brett
>> >
>> > 2008/7/28 Dan Dare <da...@gmail.com>:
>> >>
>> >> 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 <am...@gmail.com>:
>> >>>> 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
>> > <dj...@sofaxis.com>
>> >>>> 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
>> > firstrandbankdisclaimer@fnb.co.za 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
>> firstrandbankdisclaimer@fnb.co.za and we will send you a copy of the
>> Disclaimer.
>>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Mark Johnson <am...@gmail.com>.
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?
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
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
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
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 <MJ...@fnb.co.za> 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:brett.porter@gmail.com]
> Sent: 28 July 2008 15:16
> To: users@archiva.apache.org
> 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 <MJ...@fnb.co.za>:
> > 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:brett.porter@gmail.com]
> > Sent: 28 July 2008 14:14
> > To: users@archiva.apache.org
> > 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>
> > agon/wagon-provider-api/1.0-beta-4/wagon-provider-api-1.0-beta-4.jar
> >
> > Cheers,
> > Brett
> >
> > 2008/7/28 Dan Dare <da...@gmail.com>:
> >>
> >> 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 <am...@gmail.com>:
> >>>> 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
> > <dj...@sofaxis.com>
> >>>> 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
> > firstrandbankdisclaimer@fnb.co.za 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
> firstrandbankdisclaimer@fnb.co.za and we will send you a copy of the
> Disclaimer.
>
RE: Upgrade from 1.0 to 1.1 : network problem
Posted by "Jeffery, Mark" <MJ...@fnb.co.za>.
This build
http://vmbuild.apache.org/continuum/workingCopy.action?projectId=652&use
rDirectory=target
resolves the issue.
Thanks
Jeff
-----Original Message-----
From: Brett Porter [mailto:brett.porter@gmail.com]
Sent: 28 July 2008 15:16
To: users@archiva.apache.org
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
Cheers,
Brett
2008/7/28 Jeffery, Mark <MJ...@fnb.co.za>:
> 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:brett.porter@gmail.com]
> Sent: 28 July 2008 14:14
> To: users@archiva.apache.org
> 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
> agon/wagon-provider-api/1.0-beta-4/wagon-provider-api-1.0-beta-4.jar
>
> Cheers,
> Brett
>
> 2008/7/28 Dan Dare <da...@gmail.com>:
>>
>> 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 <am...@gmail.com>:
>>>> 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
> <dj...@sofaxis.com>
>>>> 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
> firstrandbankdisclaimer@fnb.co.za 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
firstrandbankdisclaimer@fnb.co.za and we will send you a copy of the Disclaimer.
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Brett Porter <br...@gmail.com>.
Perhaps you could try building from source, or the following build:
http://vmbuild.apache.org/continuum/workingCopy.action?projectId=652&userDirectory=target
Cheers,
Brett
2008/7/28 Jeffery, Mark <MJ...@fnb.co.za>:
> 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:brett.porter@gmail.com]
> Sent: 28 July 2008 14:14
> To: users@archiva.apache.org
> 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
> agon/wagon-provider-api/1.0-beta-4/wagon-provider-api-1.0-beta-4.jar
>
> Cheers,
> Brett
>
> 2008/7/28 Dan Dare <da...@gmail.com>:
>>
>> 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 <am...@gmail.com>:
>>>> 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
> <dj...@sofaxis.com>
>>>> 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
> firstrandbankdisclaimer@fnb.co.za and we will send you a copy of the Disclaimer.
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
RE: Upgrade from 1.0 to 1.1 : network problem
Posted by "Jeffery, Mark" <MJ...@fnb.co.za>.
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:brett.porter@gmail.com]
Sent: 28 July 2008 14:14
To: users@archiva.apache.org
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
agon/wagon-provider-api/1.0-beta-4/wagon-provider-api-1.0-beta-4.jar
Cheers,
Brett
2008/7/28 Dan Dare <da...@gmail.com>:
>
> 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 <am...@gmail.com>:
>>> 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
<dj...@sofaxis.com>
>>> 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
firstrandbankdisclaimer@fnb.co.za and we will send you a copy of the Disclaimer.
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Brett Porter <br...@gmail.com>.
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/wagon/wagon-provider-api/1.0-beta-4/wagon-provider-api-1.0-beta-4.jar
Cheers,
Brett
2008/7/28 Dan Dare <da...@gmail.com>:
>
> 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 <am...@gmail.com>:
>>> 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 <dj...@sofaxis.com>
>>> 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-tp18587462p18688926.html
> Sent from the archiva-users mailing list archive at Nabble.com.
>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
Re: Upgrade from 1.0 to 1.1 : network problem
Posted by Dan Dare <da...@gmail.com>.
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 <am...@gmail.com>:
>> 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 <dj...@sofaxis.com>
>> 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-tp18587462p18688926.html
Sent from the archiva-users mailing list archive at Nabble.com.