Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-4019

ReactiveThrottler: possible starvation

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.8.0, 3.8.1
    • 3.9.0
    • None
    • None

    Description

      In production I encountered logs saying there was too much concurrent IMAP request.

      From a starting point in time, my IMAP server stopped accepting request and could not continue progress. Complete dead lock.

      By careful unit testing of ReactiveThrottler I was able to diagnose it was not handling "cancel" correctly and not propagating to items in the queue which would cause the deadlock.

      Note: one can avoid this fully by disabling IMAP throttling.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              btellier Benoit Tellier
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m