[
https://issues.apache.org/jira/browse/MRM-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Lundin updated MRM-1905:
------------------------------
Description:
Hi.
We are seeing that archiva updates the metadata before having recived the hole
file.
This manifests it self as when one build process is uploading data and another
simultaneously downloads data the downloading process sees the file being
uploaded and tries to download it before the hole file have reached archiva.
The downloading maven client then errors out with "Premature end of
Content-Length delimited message body".
One way of solving this would be to delay the metadata update until the hole
file have reached archiva.
There are no proxies involved in our case, and all the involved machines lives
in the same vmware cluster so its really unlikely that this is caused by any
other, external, issue.
was:
Hi.
We are seeing that archiva updates the metadata before having recived the hole
file.
This manifests it self as when one build process is uploading data and another
simultaneously downloads data the downloading process sees the file being
uploaded and tries to download it before the hole file have reached archiva.
The downloading maven client then errors out with "Premature end of
Content-Length delimited message body".
One way of solving this would be to delay the metadata update until the hole
file have reached archiva.
> Premature end of Content-Length delimited message body
> ------------------------------------------------------
>
> Key: MRM-1905
> URL: https://issues.apache.org/jira/browse/MRM-1905
> Project: Archiva
> Issue Type: Bug
> Components: Problem Reporting
> Reporter: Anton Lundin
>
> Hi.
> We are seeing that archiva updates the metadata before having recived the
> hole file.
> This manifests it self as when one build process is uploading data and
> another simultaneously downloads data the downloading process sees the file
> being uploaded and tries to download it before the hole file have reached
> archiva. The downloading maven client then errors out with "Premature end of
> Content-Length delimited message body".
> One way of solving this would be to delay the metadata update until the hole
> file have reached archiva.
> There are no proxies involved in our case, and all the involved machines
> lives in the same vmware cluster so its really unlikely that this is caused
> by any other, external, issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
