[
https://issues.apache.org/jira/browse/CXF-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17441312#comment-17441312
]
Andriy Redko commented on CXF-8616:
-----------------------------------
The message observer should be called in JAX-RS flows:
* Introduced new contextual property
{{PROPAGATE_202_RESPONSE_ONEWAY_OR_PARTIAL}}
* It is set to {{false}} by default but JAX-RS clients override it with
{{true}}
> Calling oneway methods using async client hangs response indefinitely
> ---------------------------------------------------------------------
>
> Key: CXF-8616
> URL: https://issues.apache.org/jira/browse/CXF-8616
> Project: CXF
> Issue Type: Bug
> Affects Versions: 3.3.11, 3.4.5
> Reporter: Andriy Redko
> Assignee: Andriy Redko
> Priority: Major
> Labels: jax-rs
> Fix For: 3.5.0, 3.4.6, 3.3.13
>
>
> It turns out that when async client (at least, the ones backed by HttpClient
> 4.x or 5.x) is used with oneway methods (in CXF context, oneway is the method
> that returns 202), the response hangs indefinitely due to the fact that the
> client callback is never called / propagated.
> {*}Update{*}: it turned out, for sync/async flows, the response filters are
> also not called for oneway methods.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
