[jira] Resolved: (CXF-1283) Forking another thread to invoke the service implementation in ServiceInvokerInterceptor is not working

["Daniel Kulp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-1283.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.5
                   2.1.8

> Forking another thread to invoke the service implementation in ServiceInvokerInterceptor is not working
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-1283
>                 URL: https://issues.apache.org/jira/browse/CXF-1283
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3
>            Reporter: Willem Jiang
>            Assignee: Daniel Kulp
>             Fix For: 2.1.8, 2.2.5
>
>
> I just did a test of using the separated thread pool for the servant execution, the test was failed. 
> It is because CXF OutgoingChainInterceptor and ServiceInvokerInterceptor are invoked in the same thread, 
> if we fork another thread to invoke the servant,  the original thread will not wait for the response message 
> and keep on calling the OutgoingChainInterceptor and the OutgoingChainInterceptor can't get the outMessage
>  from the exchange the output stream will be closed. The client side will not get the expected message then.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.