cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joao Silva de Melo (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CXF-7475) HttpConduit enabled Bus blocks indefinitely on pending requests after shutdown
Date Tue, 15 Aug 2017 23:04:00 GMT

     [ https://issues.apache.org/jira/browse/CXF-7475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joao Silva de Melo updated CXF-7475:
------------------------------------
    Description: 
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. 

In case you cannot reproduce the issue, you might need to tweak the {{Thread.sleep(1000)}}.

  was:
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)}}.


> HttpConduit enabled Bus blocks indefinitely 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/80926c3ded0d17e1e94a72245ece2f79
> 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)

Mime
View raw message