[MNT-9770] WebDAV uploads over 2gb in size fails. Created: 14-Oct-13  Updated: 09-Apr-14  Resolved: 19-Nov-13

Status: Closed
Project: Service Packs and Hot Fixes
Component/s: WebDAV
Affects Version/s: 4.1.5
Fix Version/s: 4.1.8

Type: Service Pack Request
Reporter: Ray Walker [X] (Inactive) Assignee: Closed Bugs (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 4 days, 1 hour, 30 minutes
Original Estimate: Not Specified

Tomcat, Postgres

Attachments: Text File stack.txt    
Issue Links:
is related to by MNT-10876 Range Requests Can Fail For Files Ove... Closed
is related to by MNT-10284 File servers (FTP, WebDAV) can't hand... Closed
Bug Priority:
Category 3
ACT Numbers:


Build Location: http://releases.alfresco.com/Enterprise%204.1/4.1.8/build-00031/


Technical Description of the issue

Alfresco fails to upload files larger than 2gb using WebDAV, throwing I/O error.

Customers Description of the problem

We have been seeing issues uploading large files (2GB+) to the repository via WebDAV. We have not seen the same problems using the Java API so we believe it is an issue specifically to WebDAV. We require the upload of large 2GB+ assets to meet our functional requirements.

Supporting evidence

Replicated several times locally with .mov and .mkv files over 2gb.

Steps to reproduce

1. Mount WebDAV location(Cyberduck)
2. Navigate to Site folder folderX
3. Initiate copy of 2gb+ file to folderX

Expected Behavior

1. Upload completes, client throws no errors
2. File visible within repository

Observed Behavior
1. At 100% client throws I/O error
2. File is not staged within the repository
3. NumberFormat Exception is thrown in log

Analysis to date
Seems to be thrown by WebDAVMethod.getRequestBodyAsFile
int contentLength = req.getIntHeader(WebDAV.HEADER_CONTENT_LENGTH);
attempting int conversion against long.

Log snippet attached.

Comment by Alfresco QA Team (Inactive) [ 19-Nov-13 ]

Verified against Alfresco Enterprise v4.1.8(r57954-b848) schema 5139.

Generated at Fri Dec 04 05:06:03 GMT 2020 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.