[
https://issues.apache.org/jira/browse/ISIS-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394692#comment-17394692
]
Daniel Keir Haywood commented on ISIS-2822:
-------------------------------------------
My expectation of the contract with an Executor that when a thread is taken
from an Executor threadpool, it is leased to us in a "clean" state ... we set
up the interaction layer at the beginning and make sure it is closed before it
is returned.
Is that not the case?
> 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.3.4#803005)
