[
https://issues.apache.org/jira/browse/CXF-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235497#comment-14235497
]
Sergey Beryozkin commented on CXF-4817:
---------------------------------------
It appears to be something very subtle. CXF AbstractHttpDestination does call
ContinuationProvider complete(), in case of Servlet3Continuation it leads to an
immediate call to asyncContext.complete().
Did you have your custom listeners called before this change ?
It migh be that the current container you useis too sensitive to having a
context.complete() method being called - the exception is ignored in such cases.
Can you please investigate and check if it is the case for you ?
Cheers, Sergey
> JAX-RS AsyncResponse implementation needs to call AsyncContext.complete after
> the request is done
> -------------------------------------------------------------------------------------------------
>
> Key: CXF-4817
> URL: https://issues.apache.org/jira/browse/CXF-4817
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Reporter: Sergey Beryozkin
> Assignee: Sergey Beryozkin
> Priority: Minor
> Fix For: 2.7.4, 3.0.0-milestone1
>
>
> This will help with a better recycling of threads plus will get AsyncListener
> onComplete and onError callbacks called - for the registered completion
> callbacks be notified
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
