failed: Premature end of Content-Length delimited message body

Zeenesh Patel
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 30, 2024

I created bitbucket pipeline which triggers maven release goal to generate RPM file. To generate RPM file we have base artifact in nexus repository around size of 1GB. During pipeline execution when it tries to fetch I'm getting below error:

Unable to find/resolve artifact. Could not transfer artifact {artifactname} from/to {repopath} failed: Premature end of Content-Length delimited message body (expected: 1,042,041,480; received: 462,101,847)

I tried finding any help but couldn't found any relevant reference to fix an issue.  Can I please ask for help to fix it? Any leads would be much appreciated. 

1 answer

1 accepted

0 votes
Answer accepted
Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 1, 2024

G'day, @Zeenesh Patel 

Welcome to the community!

This error typically arises when the value of the Content-Length header does not align with the actual size of the response. This is probably due to the connection closing before receiving the entire content.

The issue appears to be linked to https://issues.apache.org/jira/browse/WAGON-486. You could try adding the following line to your code to resolve this. 

-Dmaven.wagon.http.pool=false

Let me know how it goes.

Regards,
Syahrul

Zeenesh Patel
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 4, 2024

Hi @Syahrul ,

Thank you for your answer, it really helped me pass through pipeline failure. 

Like Syahrul likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events