Uploaded image for project: 'Service Packs and Hot Fixes'
  1. Service Packs and Hot Fixes
  2. MNT-10284

File servers (FTP, WebDAV) can't handle the upload of big files (6Gb+)

    Details

    • Type: Service Pack Request
    • Status: Closed
    • Resolution: Won't Fix
    • Affects Version/s: 4.0, 4.1
    • Fix Version/s: None
    • Component/s: FTP, WebDAV
    • Labels:
      None
    • Environment:
      Tomcat 6.0.35, Windows 7, PostgreSQL,
      WebDAV clients tested : WebDrive,
      FTP : FileZilla, WinSCP
    • Bug Priority:
      Category 2
    • ACT Numbers:

      00140440

      Description

      Description

      When a large file (6Go and more) is uploaded in Alfresco using FTP or WebDAV, after the transfer to Tomcat temp directory completes, the transfer restarts on the client side and a new temp file is created.
      This keeps on happening again and again until transfer is aborted on the client or Alfresco server runs out of space.

      Note that to upload file larger than 2Go using WebDAV, MNT-9770 is needed.

      Steps to reproduce

      1- Install a vanilla Afresco 4.1.8 (v4.1.8(r57954-b848) where MNT-9770 is fixed)
      2.a- Mount WebDAV location(WebDrive, native Windows 7 WebDAV drive mount)
      2.b- Connect to Alfresco FTP server using Filezilla
      3- Navigate to Site folder folderX (either with the FTP or WebDAV client)
      4- Initiate copy of 6gb+ file to folderX

      Expected Behaviour

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

      Observed Behaviour

      1. At 100% client restart the transfer from scratch
      2. File is not staged within the repository
      3. Nothing is output in log

      Analysis to date

      I have not tested NFS but guess behavior would be the same.

      Using Cyberduck WedDAV client it seems to work better. The transfer fails showing "I/O Error: Upload failed. Read timed out" at the end of the upload. But after 5 to 10 min the file is shown in the repo.

      Note that there is a known issue with Windows client that sets WebDAV mapping drive’s capacity the same as its System Drive. So as to test with windows WebDAV native mount drive you will need to make sure that the space on the client system drive is sufficient :
      See http://support.microsoft.com/kb/2386902 for more information.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedissues Closed Issues
                  Reporter:
                  croux Corentin Roux [X] (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 2 days, 6 hours
                    2d 6h

                      Structure Helper Panel