[ 
https://issues.apache.org/jira/browse/WAGON-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265717#comment-17265717
 ] 

Arul Elvis J commented on WAGON-603:
------------------------------------

[~michael-o]  PFA with system.debug=true along with batch mode 
[^failed_logs-batch-wired_jan15.txt]

 

I can see detailed HTTP logging as below:

 

[DEBUG] Connection request: [route: 
\{s}->https://repo.maven.apache.org:443][total kept alive: 1; route allocated: 
5 of 20; total allocated: 5 of 40]
2021-01-15T03:35:23.2584394Z [DEBUG] Connection leased: [id: 122][route: 
\{s}->https://repo.maven.apache.org:443][total kept alive: 0; route allocated: 
5 of 20; total allocated: 5 of 40]
2021-01-15T03:35:23.2585181Z [DEBUG] http-outgoing-122: set socket timeout to 0
2021-01-15T03:35:23.2585699Z [DEBUG] http-outgoing-122: set socket timeout to 
1800000
2021-01-15T03:35:23.2586397Z [DEBUG] Executing request GET 
/maven2/com/fasterxml/jackson/core/jackson-core/2.9.6/jackson-core-2.9.6.jar.sha1
 HTTP/1.1

 

Looking for something else ? 

> Connection reset error from Azure pipelines
> -------------------------------------------
>
>                 Key: WAGON-603
>                 URL: https://issues.apache.org/jira/browse/WAGON-603
>             Project: Maven Wagon
>          Issue Type: Bug
>         Environment: In both Ubuntu and Windows agent specification
>            Reporter: Arul Elvis J
>            Priority: Blocker
>             Fix For: waiting-for-feedback
>
>         Attachments: failed_logs-batch-wired.txt, 
> failed_logs-batch-wired_jan15.txt, failed_logs-batch-wired_jan15.txt, 
> failed_logs-batch-wired_latest.txt, logs_143613.zip
>
>   Original Estimate: 408h
>  Remaining Estimate: 408h
>
> When the pipelines are executed in Azure pipelines, we are facing connection 
> reset error. Azure pipelines team claims that connection is closed from Maven 
> central repo end. Below is the error message. Have attached the complete log 
> zip file for your reference. Can you please prioritize as soon as possible, 
> as it is impacting all the pipelines including the production builds ?
>  
> {{-------------------------------------------------------------------- }}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-resources-plugin:3.0.2:resources 
> (default-resources) on project bata-s-sfdc-deferredpromo: Execution 
> default-resources of goal 
> org.apache.maven.plugins:maven-resources-plugin:3.0.2:resources failed: 
> Plugin org.apache.maven.plugins:maven-resources-plugin:3.0.2 or one of its 
> dependencies could not be resolved: Failed to collect dependencies at 
> org.apache.maven.plugins:maven-resources-plugin:jar:3.0.2 -> 
> org.apache.maven:maven-plugin-api:jar:3.0 -> 
> org.sonatype.sisu:sisu-inject-plexus:jar:1.4.2 -> 
> org.codehaus.plexus:plexus-component-annotations:jar:1.6: Failed to read 
> artifact descriptor for 
> org.codehaus.plexus:plexus-component-annotations:jar:1.6: Could not transfer 
> artifact org.codehaus.plexus:plexus-component-annotations:pom:1.6 from/to 
> central ([https://repo.maven.apache.org/maven2)]: Connection reset -> [Help 
> 1] 
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch. 
> [ERROR] Re-run Maven using the -X switch to enable full debug logging. 
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles: 
> [ERROR] [Help 1] 
> [http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException] 
> The process 
> 'C:\ProgramData\chocolatey\lib\maven\apache-maven-3.6.3\bin\mvn.cmd' failed 
> with exit code 1 
> Could not retrieve code analysis results - Maven run failed. 
> {{##[error]Build failed. }}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to