[
https://issues.apache.org/jira/browse/MRESOLVER-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-361:
--------------------------------------
Description:
Two issues reported:
* PUT on closed connection is not retried. Suggested fix: change retry handler
to one that treats PUT as idempotent.
* -Oddity with 1 vs 2+ checksum algorithm used, in first case checksum upload
failure fails whole build, in second it only warns.- This proved wrong, user
build failed as metadata (so "main" payload not checksum of the main payload)
failed due HTTP 500 response from server.
was:
Two issues reported:
* PUT on closed connection is not retried. Suggested fix: change retry handler
to one that treats PUT as idempotent.
* Oddity with 1 vs 2+ checksum algorithm used, in first case checksum upload
failure fails whole build, in second it only warns.
> Unreliable TCP and retries on upload
> ------------------------------------
>
> Key: MRESOLVER-361
> URL: https://issues.apache.org/jira/browse/MRESOLVER-361
> Project: Maven Resolver
> Issue Type: Task
> Affects Versions: 1.9.10
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.11
>
>
> Two issues reported:
> * PUT on closed connection is not retried. Suggested fix: change retry
> handler to one that treats PUT as idempotent.
> * -Oddity with 1 vs 2+ checksum algorithm used, in first case checksum
> upload failure fails whole build, in second it only warns.- This proved
> wrong, user build failed as metadata (so "main" payload not checksum of the
> main payload) failed due HTTP 500 response from server.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
