[infinispan-issues] [JBoss JIRA] (ISPN-10075) We should ensure that when CompletionStages are completed they are continued only on Infinispan threads

[Will Burns (Jira)]

     [ https://issues.redhat.com/browse/ISPN-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will Burns resolved ISPN-10075.
-------------------------------
    Resolution: Duplicate Issue


This was handled in https://issues.redhat.com/browse/ISPN-11543

> We should ensure that when CompletionStages are completed they are continued only on Infinispan threads
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-10075
>                 URL: https://issues.redhat.com/browse/ISPN-10075
>             Project: Infinispan
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Will Burns
>            Assignee: Will Burns
>            Priority: Major
>
> When a user can supply a CompletionStage to delay operations this can cause a possibility of that being completed on a different thread than expected. The new non blocking listeners will especially be affected by this (ISPN-9614). This is also problematic for CacheLoader SPI and any future API that takes a Publisher as an argument from the user.
> This issue should at least fix the upcoming non blocking listeners as discussed at https://github.com/infinispan/infinispan/pull/6401#issuecomment-475181484.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)