[
https://issues.apache.org/jira/browse/ISIS-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386711#comment-17386711
]
Andi Huber commented on ISIS-2822:
----------------------------------
Why is this an issue? An async execution is running with its own exclusive
interaction context, and there must never be a transaction, that is shared
among interaction contexts.
> 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-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)
