Uploaded image for project: 'Isis'
  1. Isis
  2. ISIS-2822

Wrapper: async executions must run within their own exclusive transaction

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-M7
    • Component/s: Isis Core
    • Labels:
      None

      Description

      Ideally to be enforced by running on a different (isolated) thread.
      Yet we are using the fork-join common pool, which provides no such guarantee.

      Currently an async execution might eventually run on the same thread as the caller, and hence participate in the same transaction as the caller. The framework must prevent this from happening.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                hobrom Andi Huber
                Reporter:
                hobrom Andi Huber
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: