Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-27346

Don't timeout during long imports

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 9.10, 10.10
    • Fix Version/s: 9.10-HF37, 10.10-HF15, 11.1
    • Component/s: S3, Web UI
    • Release Notes Summary:
      Long imports now use an extended timeout.
    • Tags:
    • Backlog priority:
      900
    • Upgrade notes:
      Hide

      Following this fix, it is no more possible to call FileManager.Import in a sychronous event, it has to be done in an asynchronous event. See NXP-28534

      Show
      Following this fix, it is no more possible to call FileManager.Import in a sychronous event, it has to be done in an asynchronous event. See NXP-28534
    • Sprint:
      nxFG 11.1.9, nxFG 11.1.10

      Description

      Long uploads to S3 via the Web UI fail.

      Two different problems have been identified. After some analysis, we believe the following can happen:

      1. direct upload sends large files to S3, then the execution of the import is requested to Nuxeo; if the import (FileManager.Import operation) takes longer than the transaction timeout then it will fail.

      2. direct upload of large files sends them directly from the browser to S3; while this is ongoing no interactions with the Nuxeo server happen therefore after some time (default 1h) the HTTP session times out; after the direct upload is finished some browser interaction with the server is supposed to happen but fails because there is no session anymore so no authentication and the browser gets a 401 or 403 (prompting for basic auth).

      For 1. the solution is to do the import in a transaction with a very long timeout to avoid import timeouts. This ticket will deal with this.

      For 2. there is no immediate solution, but a simple workaround is to increase the HTTP session timeout (session.timeout in nuxeo.conf, expressed in minutes; the default is 60).

      To completely avoid 2. the UI should have something regular contact with the server while the direct upload is ongoing, to avoid session timeouts. This will have to be the work of another ticket (NXP-28114).

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 hours
                  3h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.