Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Tue, 15 Aug 2017 23:04:00 +0000 (UTC)
From: "Joao Silva de Melo (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.13094895.1502838014000.38041.1502838240820@Atlassian.JIRA>
In-Reply-To: <JIRA.13094895.1502838014000@Atlassian.JIRA>
References: <JIRA.13094895.1502838014000@Atlassian.JIRA> <JIRA.13094895.1502838014036@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CXF-7475) HttpConduit enabled Bus blocks
 indefinitely on pending requests after shutdown
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 15 Aug 2017 23:04:12 -0000


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

Joao Silva de Melo updated CXF-7475:
------------------------------------
    Description:=20
Ol=C3=A1

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 i=
t causes requests to hang on the {{AsyncHTTPConduit.AsyncWrappedOutputStrea=
m::getHttpResponse}} indefinitely.

*How to reproduce*

This is an edge case, but it happens when the Bus is shutdown after the cli=
ent started the request but before getting the ConnectException. Below ther=
e 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.=20

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

  was:
Ol=C3=A1

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 i=
t causes requests to hang on the {{AsyncHTTPConduit.AsyncWrappedOutputStrea=
m::getHttpResponse}} indefinitely.

*How to reproduce*

This is an edge case, but it happens when the Bus is shutdown after the cli=
ent started the request but before getting the ConnectException. Below ther=
e 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.=20

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


> HttpConduit enabled Bus blocks indefinitely on pending requests after shu=
tdown
> -------------------------------------------------------------------------=
-----
>
>                 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=C3=A1
> Just found out an issue with shutting down the {{Bus}} when configured wi=
th {{AsyncHttpConduit}}.
> *Problem*
> In case it happens, applications won't be able to gracefully shutdown, as=
 it causes requests to hang on the {{AsyncHTTPConduit.AsyncWrappedOutputStr=
eam::getHttpResponse}} indefinitely.
> *How to reproduce*
> This is an edge case, but it happens when the Bus is shutdown after the c=
lient started the request but before getting the ConnectException. Below th=
ere 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();}}, th=
at is, waiting for the request thread to do it's job.=20
> In case you cannot reproduce the issue, you might need to tweak the {{Thr=
ead.sleep(1000)}}.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)