[ https://issues.apache.org/jira/browse/WAGON-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963114#comment-16963114 ]
Michael Osipov edited comment on WAGON-568 at 10/30/19 3:22 PM: ---------------------------------------------------------------- My bad, it should have been BAIS. I cannot fully isolate the issue with the copy loop, it must be related to the channels and the socket output stream, but I was able to modiy a Wagon unit test for this. Please check out from the Wagon repo branch {{WAGON-568_block}}, run {{mvn clean verify}} and you shall see {{HttpWagonTest}#testRedirectPutFromStreamWithFullUrl()} fail. The surefire output includes complete wire logging. The input streams are reused w/o being reset (programming error). HttpClient blocks for some reason during read and Jetty issues a {{TimeoutException}} after 30 s. The very same {{writeTo()}} isolated w/o any network interaction runs perfectly and returns -1 when the stream is exhausted. I would HttpClient expect to instantly fail with {{Cannot retry non-repeatable request}} as happens in {{#testRedirectPutFromStreamRelativeUrl()}}. was (Author: michael-o): My bad, it should have been BAIS. I cannot fully isolate the issue which the copy loop, it must be related to the channels and the socket output stream. But I was able to modiy a Wagon unit test for this. Please check out from the Wagon repo branch {{WAGON-568_block}}, run {{mvn clean verify}} and you shall see {{HttpWagonTest}#testRedirectPutFromStreamWithFullUrl()} fail. The surefire output includes complete wire logging. The input streams are reusing w/o being reset (programming error). HttpClient blocks for some reason during read and Jetty issues a {{TimeoutException}} after 30 s. The very same {{writeTo()}} isolated w/o any network interaction runs perfectly and returns -1 when the stream is exhausted. I would HttpClient expect to instantly fail with {{Cannot retry non-repeatable request}} as happens in {{#testRedirectPutFromStreamRelativeUrl()}}. > Fail to deploy on Sonatype OSS since maven 3.5.4 > ------------------------------------------------ > > Key: WAGON-568 > URL: https://issues.apache.org/jira/browse/WAGON-568 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http > Affects Versions: 3.3.3 > Environment: 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 > PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64 > openjdk version "1.8.0_202" > OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_202-b08) > OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.202-b08, mixed mode) > Reporter: Stephane Landelle > Priority: Major > > I've been trying to release AsyncHttpClient for days and deployment was > always super slow until it ultimately failed or completely stalled. > The issue seems to be that maven-deploy-plugin wants to upload checksum > files. I have no idea where those would come from, as far as I know, those > are generated by the maven repository. > > {code:java} > [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ > async-http-client-project --- > Uploading to sonatype-nexus-staging: > http://oss.sonatype.org/service/local/staging/deploy/maven2/org/asynchttpclient/async-http-client-project/2.0.40/async-http-client-project-2.0.40.pom > [WARNING] Failed to upload checksum > org/asynchttpclient/async-http-client-project/2.0.40/async-http-client-project-2.0.40.pom.sha1: > null{code} > > > For each actual file, maven-deploy-plugin tries to upload a sha1 and a md5 > files and this takes forever to ultimately fail. > I tried upgrading plugins but nothing worked. > I finally found [this > ticket|[https://issues.sonatype.org/browse/OSSRH-43371?focusedCommentId=610865&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-610865]] > against Sonatype OSS describing the exact same behavior and stating > downgrading to maven 3.5.3 fixed the issue. > Indeed, downgrading did the trick! > I'm opening an issue here and not against OSS Sonatype as it looks like a > maven regression to me. > * maven 3.6.2: fails > * maven 3.5.4: fails > * maven 3.5.3: works like a charm -- This message was sent by Atlassian Jira (v8.3.4#803005)