You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@isis.apache.org by "Andi Huber (Jira)" <ji...@apache.org> on 2021/07/24 12:32:00 UTC

[jira] [Created] (ISIS-2822) Wrapper: async executions must run within their own exclusive transaction

Andi Huber created ISIS-2822:
--------------------------------

             Summary: Wrapper: async executions must run within their own exclusive transaction
                 Key: ISIS-2822
                 URL: https://issues.apache.org/jira/browse/ISIS-2822
             Project: Isis
          Issue Type: Bug
          Components: Isis Core
            Reporter: Andi Huber
            Assignee: Andi Huber
             Fix For: 2.0.0-M6


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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)