[
https://issues.apache.org/jira/browse/CXF-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235473#comment-14235473
]
Erwan Fouret commented on CXF-4817:
-----------------------------------
Thanks for your quick reply.
{{javax.ws.rs.container.CompletionCallback.onComplete()}} is called but
{{javax.servlet.AsyncContext.complete()}} is not and thus any
{{javax.servlet.AsyncListener}} declared (e.g. inside a servlet filter) won't
see a call to {{onComplete()}}.
It seems the code initially committed to fix this issue resulted in calling
{{AsyncContext.complete()}} (through {{Servlet3ContinuationProvider.reset()}})
which is no longer the case.
> 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)
