You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Joao Silva de Melo (JIRA)" <ji...@apache.org> on 2017/08/15 23:01:00 UTC
[jira] [Created] (CXF-7475) HttpConduit enabled bus hanging on
pending requests after shutdown
Joao Silva de Melo created CXF-7475:
---------------------------------------
Summary: HttpConduit enabled bus hanging on pending requests after shutdown
Key: CXF-7475
URL: https://issues.apache.org/jira/browse/CXF-7475
Project: CXF
Issue Type: Bug
Components: Bus, Transports
Affects Versions: 3.1.12
Reporter: Joao Silva de Melo
Priority: Critical
Olá
Just found out an issue with shutting down the {{Bus}} when configured with {{AsyncHttpConduit}}.
*Problem*
In case it happens, applications won't be able to gracefully shutdown, as it causes requests to hang on the {{AsyncHTTPConduit.AsyncWrappedOutputStream::getHttpResponse}} indefinitely.
*How to reproduce*
This is an edge case, but it happens when the Bus is shutdown after the client started the request but before getting the ConnectException. Below there is a link to a Junit test reproducing the problem.
https://gist.github.com/dwp-joaomelo/8e2f6f916501a896a2beeae86fc4d5a8
The test should hang forever on the last statement {{thread.join();}}, that is, waiting for the request thread to do it's job.
In case you cannot reproduce the issue, you might need to tweak the {{Thread.sleep(1000)}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)