[
https://issues.apache.org/jira/browse/CXF-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko updated CXF-8616:
------------------------------
Description:
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.
was:
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 it 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.
> 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
> 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)
