[jira] [Work logged] (CXF-8242) Stop blocking executor thread on microprofile rest asynchronous call

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-8242?focusedWorklogId=407524&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-407524 ]

ASF GitHub Bot logged work on CXF-8242:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Mar/20 00:35
            Start Date: 22/Mar/20 00:35
    Worklog Time Spent: 10m 
      Work Description: reta commented on pull request #654: CXF-8242: Stop blocking executor thread on microprofile rest asynchronous call
URL: https://github.com/apache/cxf/pull/654
 
 
   Replacing CXF's future implementation with Java 8 `CompletableFuture` delegate. **Note:** still work in progress, assessing the implication on threading / synchronization. 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 407524)
    Remaining Estimate: 0h
            Time Spent: 10m

> Stop blocking executor thread on microprofile rest asynchronous call  
> ----------------------------------------------------------------------
>
>                 Key: CXF-8242
>                 URL: https://issues.apache.org/jira/browse/CXF-8242
>             Project: CXF
>          Issue Type: Bug
>          Components: MicroProfile
>    Affects Versions: 3.3.5
>            Reporter: Baptiste AIGLIN
>            Assignee: Andriy Redko
>            Priority: Critical
>         Attachments: cxf-microprofile.zip
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Hello, while digging into the way implementation for microprofile was done to understand how I can override the default executor and how it is used behind the scene, I found that the microprofile futures are actually created using CompletableFuture.supplyAsync using the given executor or default one defined by CXF and calling wait on it. If not mistaken this should block the executor thread until it is resumed by async handler. This is a major issue for us as we were expecting pure asynchronous processing to avoid defining executors with many threads.
> If everything I say is correct I have tried to implement a naive implementation creating a future using constructor that is not waiting but will be completed by asynchronous handler



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