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

Better manage Seam Conversation concurrency

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.8
    • Component/s: Seam / JSF UI

      Description

      In some cases, Seam page rendering can fail because of the Conversation locking system and a ConcurrentRequetsTimeout exception is visible in logs.

      See : http://doc.nuxeo.com/display/NXDOC/I+get+an+error+when+I+click+on+two+links+quickly

      The root of the problem is that the way Seam handles the conversation concurrency is not ideal.

      We can surely do better :

      • try to choose the victim : kill the old request and not the new one
        or
      • create a temporary conversation that has a change to run : re-init a minimal context
        or
      • reduce critical section size
        ...

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

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