[
https://issues.apache.org/jira/browse/CXF-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235691#comment-14235691
]
Sergey Beryozkin commented on CXF-4817:
---------------------------------------
Calling startAsync is the only way, as far as I know, to ensure that multiple
timeouts (those managed by TimeoutHandler) work.
However, I think we can try and optionally avoid restarting a context if a
contextual property is set, for example, if the application knows
TimeoutHandler, if any, will never re-suspend the continuation, then setting a
property would do.
> 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)
