[
https://issues.apache.org/jira/browse/CXF-7475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151428#comment-16151428
]
Dennis Kieselhorst commented on CXF-7475:
-----------------------------------------
Tried your testcase several times but never hit the issue. Could you please
attach a thread dump with stacktrace? Is it hanging in wait()?
> HttpConduit enabled Bus blocks pending requests indefinitely 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: Blocker
>
> 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/80926c3ded0d17e1e94a72245ece2f79
> The test should hang forever on the last statement {{thread.join();}}, that
> is, waiting for the request thread to do it's job.
> Note that you might need to run it a couple of times as it is a timing thing,
> 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)
