[ 
https://issues.apache.org/jira/browse/CXF-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15619544#comment-15619544
 ] 

ASF GitHub Bot commented on CXF-7112:
-------------------------------------

GitHub user tadayosi opened a pull request:

    https://github.com/apache/cxf/pull/188

    [CXF-7112,CXF-7109] Make sure to remove ClientCallback from exchange when 
invoking handleException()

    https://issues.apache.org/jira/browse/CXF-7112
    https://issues.apache.org/jira/browse/CXF-7109
    
    If a client callback is not removed from exchange, there still remains a 
possibility for some other thread somewhere else to invoke the same callback 
again, according to [CXF-7109](https://issues.apache.org/jira/browse/CXF-7109).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tadayosi/cxf CXF-7112

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cxf/pull/188.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #188
    
----
commit 1d67c14d413c0ead5daa3ac5d1a0e5e8ad3145ec
Author: Tadayoshi Sato <[email protected]>
Date:   2016-10-30T08:07:40Z

    [CXF-7112,CXF-7109] Make sure to remove ClientCallback from exchange when 
invoking handleException()

----


> AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api
> -------------------------------------------------------------------
>
>                 Key: CXF-7112
>                 URL: https://issues.apache.org/jira/browse/CXF-7112
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 3.2.0, 3.1.9
>
>
> As for the ahc we should use the application level way to check the 
> ReceiveTimeout to let ahc connectionManager to manage the connection 
> lifecycle for a better performance.
> This works with jaxws sync api and AsyncHTTPConduit.getHttpResponse have this 
> timeout check(AsyncHTTPConduitTest.testTimeout cover this scenario), but with 
> jaxws async api we don't have this timeout check for ahc, we need provide one



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to