You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/10/31 10:16:00 UTC
[jira] [Comment Edited] (MRESOLVER-55) Artifact download failures
[ https://issues.apache.org/jira/browse/MRESOLVER-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668644#comment-16668644 ]
Michael Osipov edited comment on MRESOLVER-55 at 10/31/18 10:15 AM:
--------------------------------------------------------------------
[~michael-o] There are no errors in our artifactory.log and there is nothing in our artifactory request log except for lines with 200(OK) so I don't think the artifactory is even seeing the request that fails. The errors happen on our CI system when multiple builds are going on so I think it is due to network congestion. Sorry, but I am not sure what you mean by "fully on your side".
In the build log just before the connect timeout occurs there is this info:
{noformat}
[12:09:36]W: [<ourgid>:<ourartifactid>] FINE: http-outgoing-6 << Content-Length: 40
[12:09:36]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:09:36 PM org.apache.maven.wagon.providers.http.httpclient.headers onResponseReceived
[12:09:36]W: [<ourgid>:<ourartifactid>] FINE: http-outgoing-6 << Date: Tue, 30 Oct 2018 12:08:42 GMT
[12:09:36]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:09:36 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec execute
[12:09:36]W: [<ourgid>:<ourartifactid>] FINE: Connection can be kept alive indefinitely
[12:09:36]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:09:36 PM org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager releaseConnection
[12:09:36]W: [<ourgid>:<ourartifactid>] FINE: Connection [id: 6][route: \{s}->https://<ourdomain>:<ourport> can be kept alive indefinitely
[12:09:36]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:09:36 PM org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager releaseConnection
[12:09:36]W: [<ourgid>:<ourartifactid>] FINE: Connection released: [id: 6][route: \{s}->https://<ourdomain>:<ourport>][total kept alive: 3; route allocated: 4 of 20; total allocated: 4 of 40]
[12:09:36] : [Step 2/8] [INFO] Downloaded: https://<ourdomain>:<ourport>/<full artifactory path to the jar>.jar (3806 KB at 116.0 KB/sec)
[12:10:03]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:10:03 PM org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultManagedHttpClientConnection shutdown
[12:10:03]W: [<ourgid>:<ourartifactid>] FINE: http-outgoing-8: Shutdown connection
[12:10:03]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:10:03 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec abortConnection
[12:10:03]W: [<ourgid>:<ourartifactid>] FINE: Connection discarded
[12:10:03]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:10:03 PM org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultManagedHttpClientConnection close
[12:10:03]W: [<ourgid>:<ourartifactid>] FINE: http-outgoing-8: Close connection
[12:10:03]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:10:03 PM org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager releaseConnection
[12:10:03]W: [<ourgid>:<ourartifactid>] FINE: Connection released: [id: 8][route: \{s}->https://<ourdomain>:<ourport>][total kept alive: 3; route allocated: 3 of 20; total allocated: 3 of 40]
[12:10:11] : [Step 2/8] [Maven Watcher]
[12:10:11]E: [Step 2/8] Failed to execute goal on project <our project>: Could not resolve dependencies for project <ourgid>:<ourartifactid>:pom:<version>: Could not transfer artifact <somegid>:<someartifactid>:jar:<someversion> from/to <our repository name> (https://<ourdomain>:<ourport>/<our repository>): Connect to <ourdomain>:<ourport> [<ourdomain>/<our IP>] failed: connect timed out
{noformat}
The settings.xml contains the following:
{code:xml}
<httpConfiguration>
<all>
<connectionTimeout>60000</connectionTimeout>
<readTimeout>60000</readTimeout>
<usePreemptive>true</usePreemptive>
</all>
</httpConfiguration>
{code}
I dont see anything in the build log showing +any+ retries for connect.
was (Author: gordon.cody@zafin.com):
[~michael-o] There are no errors in our artifactory.log and there is nothing in our artifactory request log except for lines with 200(OK) so I don't think the artifactory is even seeing the request that fails. The errors happen on our CI system when multiple builds are going on so I think it is due to network congestion. Sorry, but I am not sure what you mean by "fully on your side".
In the build log just before the connect timeout occurs there is this info:
[12:09:36]W: [<ourgid>:<ourartifactid>] FINE: http-outgoing-6 << Content-Length: 40
[12:09:36]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:09:36 PM org.apache.maven.wagon.providers.http.httpclient.headers onResponseReceived
[12:09:36]W: [<ourgid>:<ourartifactid>] FINE: http-outgoing-6 << Date: Tue, 30 Oct 2018 12:08:42 GMT
[12:09:36]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:09:36 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec execute
[12:09:36]W: [<ourgid>:<ourartifactid>] FINE: Connection can be kept alive indefinitely
[12:09:36]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:09:36 PM org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager releaseConnection
[12:09:36]W: [<ourgid>:<ourartifactid>] FINE: Connection [id: 6][route: \{s}->https://<ourdomain>:<ourport> can be kept alive indefinitely
[12:09:36]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:09:36 PM org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager releaseConnection
[12:09:36]W: [<ourgid>:<ourartifactid>] FINE: Connection released: [id: 6][route: \{s}->https://<ourdomain>:<ourport>][total kept alive: 3; route allocated: 4 of 20; total allocated: 4 of 40]
[12:09:36] : [Step 2/8] [INFO] Downloaded: https://<ourdomain>:<ourport>/<full artifactory path to the jar>.jar (3806 KB at 116.0 KB/sec)
[12:10:03]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:10:03 PM org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultManagedHttpClientConnection shutdown
[12:10:03]W: [<ourgid>:<ourartifactid>] FINE: http-outgoing-8: Shutdown connection
[12:10:03]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:10:03 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec abortConnection
[12:10:03]W: [<ourgid>:<ourartifactid>] FINE: Connection discarded
[12:10:03]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:10:03 PM org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultManagedHttpClientConnection close
[12:10:03]W: [<ourgid>:<ourartifactid>] FINE: http-outgoing-8: Close connection
[12:10:03]W: [<ourgid>:<ourartifactid>] Oct 30, 2018 12:10:03 PM org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager releaseConnection
[12:10:03]W: [<ourgid>:<ourartifactid>] FINE: Connection released: [id: 8][route: \{s}->https://<ourdomain>:<ourport>][total kept alive: 3; route allocated: 3 of 20; total allocated: 3 of 40]
[12:10:11] : [Step 2/8] [Maven Watcher]
[12:10:11]E: [Step 2/8] Failed to execute goal on project <our project>: Could not resolve dependencies for project <ourgid>:<ourartifactid>:pom:<version>: Could not transfer artifact <somegid>:<someartifactid>:jar:<someversion> from/to <our repository name> (https://<ourdomain>:<ourport>/<our repository>): Connect to <ourdomain>:<ourport> [<ourdomain>/<our IP>] failed: connect timed out
The settings.xml contains the following:
<httpConfiguration>
<all>
<connectionTimeout>60000</connectionTimeout>
<readTimeout>60000</readTimeout>
<usePreemptive>true</usePreemptive>
</all>
</httpConfiguration>
I dont see anything in the build log showing +any+ retries for connect.
> Artifact download failures
> --------------------------
>
> Key: MRESOLVER-55
> URL: https://issues.apache.org/jira/browse/MRESOLVER-55
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
> Affects Versions: Maven Artifact Resolver 1.1.1
> Environment: Windows, Ubuntu
> Reporter: Lasse Westh-Nielsen
> Priority: Major
> Fix For: waiting-for-feedback
>
>
> Hey,
> We often run Maven builds of [https://github.com/neo4j/neo4j] on machines with cold caches/ empty ~/.m2/repository folders.
> There are rather a lot of dependencies to download, so even though the failure rate of individual artifact downloads is small, at our scale it causes significant build failures.
> I am working on seeding caches. Separately though it would be great to be able to configure retries and timeouts for dependency downloads - optimise for build throughput rather than latency as it were.
> How do I do that? I can't find it documented anywhere, and trying to browse "wagon" source code got me nowhere.
> Regards,
> Lasse
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)