0

Archiva 2.2.0. is up and running on a VM (CentOS 6.6). The VM can access the internet behind a proxy.

For example, GET repo1.maven.org works well:

...
<body>
        <div id="top"></div>
        <div id="container">
        <p>Browsing for this directory has been disabled.</p>
        <p><a href="http://search.maven.org/#browse">View</a> this directory's contents on <a href="http://search.maven.org/#browse">http://search.maven.org</a> instead.</p>
        <p>Find out more about <a href="http://central.sonatype.org">The Central Repository</a>.</p>
        <div id="footer-spacer"></div>
    </div>
    <div id="footer">
        <a href="http://central.sonatype.org">About Central</a>&nbsp;|&nbsp;<a href="/terms.html">Terms of Service</a>
    </div>
</body>
...

Two remote repositories are configured, both with the same proxy.

enter image description here

But unfortunately, I always get the same connection timeout exception. See below the exception for one of the configured remote repository (Central).

From archiva.log:

2015-06-01 10:24:55,286 [taskScheduler#indexDownloadRemote-1] INFO  org.apache.archiva.scheduler.indexing.DownloadRemoteIndexTask$DownloadListener [] - error of transfer file nexus-maven-repository-index.properties: Connect to repo1.maven.org:80 timed out
org.apache.maven.wagon.TransferFailedException: Connect to repo1.maven.org:80 timed out
        at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:892) ~[wagon-http-2.5.jar:2.5]
        at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) [wagon-provider-api-2.5.jar:2.5]
        at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) [wagon-provider-api-2.5.jar:2.5]
        at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) [wagon-provider-api-2.5.jar:2.5]
        at org.apache.archiva.scheduler.indexing.DownloadRemoteIndexTask$WagonResourceFetcher.retrieve(DownloadRemoteIndexTask.java:351) [archiva-scheduler-indexing-2.2.0.jar:?]
        at org.apache.maven.index.updater.DefaultIndexUpdater.downloadIndexProperties(DefaultIndexUpdater.java:459) [indexer-core-5.1.1.jar:5.1.1]
        at org.apache.maven.index.updater.DefaultIndexUpdater.access$000(DefaultIndexUpdater.java:76) [indexer-core-5.1.1.jar:5.1.1]
        at org.apache.maven.index.updater.DefaultIndexUpdater$IndexAdaptor.setProperties(DefaultIndexUpdater.java:589) [indexer-core-5.1.1.jar:5.1.1]
        at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:814) [indexer-core-5.1.1.jar:5.1.1]
        at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:136) [indexer-core-5.1.1.jar:5.1.1]
        at org.apache.archiva.scheduler.indexing.DownloadRemoteIndexTask.run(DownloadRemoteIndexTask.java:186) [archiva-scheduler-indexing-2.2.0.jar:?]
        at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-4.1.4.RELEASE.jar:4.1.4.RELEASE]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [?:1.7.0_65]
        at java.util.concurrent.FutureTask.run(FutureTask.java:262) [?:1.7.0_65]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) [?:1.7.0_65]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) [?:1.7.0_65]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [?:1.7.0_65]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [?:1.7.0_65]
        at java.lang.Thread.run(Thread.java:745) [?:1.7.0_65]
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to repo1.maven.org:80 timed out
        at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119) ~[httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177) ~[httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304) ~[httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611) ~[httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446) ~[httpclient-4.3.6.jar:4.3.6]

From request-*.log:

IP -  -  [01/juin/2015:08:47:55 +0000] "GET /restServices/archivaServices/remoteRepositoriesService/checkRemoteConnectivity/central?_=1433145022958 HTTP/1.1" 200 5 "http://$$$$$$$$$$/" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36"
IP -  -  [01/juin/2015:08:46:54 +0000] "GET /restServices/archivaServices/remoteRepositoriesService/checkRemoteConnectivity/repo.jenkins-ci.org?_=1433145022952 HTTP/1.1" 200 5 "http://$$$$$$$$$$/" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36"

Am I missing something? Thanks!

tduchateau
  • 4,351
  • 2
  • 29
  • 40

1 Answers1

0

You need to configure https://repo.maven.apache.org/maven2 and setup an https proxy.

Because even if you http://repo.maven.apache.org/maven2 there is a redirection https protocol.

That should work.

HTH Olivier

Olivier Lamy
  • 2,280
  • 1
  • 14
  • 12
  • Thanks @olamy. Artifacts download seems to work well with this configuration but not the remote check in the "remote repositories management" view. I'll investigate a bit more and keep you updated. – tduchateau Jun 03 '15 at 07:50