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/12/10 13:38:00 UTC

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

    [ https://issues.apache.org/jira/browse/ISIS-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457151#comment-17457151 ] 

Andi Huber commented on ISIS-2822:
----------------------------------

The answer is YES, iff we do get a new thread. I believe this is guaranteed for the thread-pool case. But we currently use the common fork-join pool.

> 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
>            Priority: Major
>             Fix For: 2.0.0-M7
>
>
> 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.20.1#820001)