Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
From: Adel Boutros <Adelboutros@live.com>
To: "users@qpid.apache.org " <users@qpid.apache.org>
Subject: Re: Reactor receiver stuck when transport is broken
Thread-Topic: Reactor receiver stuck when transport is broken
Thread-Index: AQHS+dn125vIP9yMTEmX4UqOt86MFqJTi82pgAAcd40=
Date: Fri, 14 Jul 2017 18:30:49 +0000
Message-ID: <VI1PR0901MB0893C01265E776019914A4F0CDAD0@VI1PR0901MB0893.eurprd09.prod.outlook.com>
References: <HK2PR06MB08174E763965D3DEF5FD47ADBBAE0@HK2PR06MB0817.apcprd06.prod.outlook.com>,<HK2PR06MB08171ADABF33A1DB0F55C5C9BBAD0@HK2PR06MB0817.apcprd06.prod.outlook.com>
In-Reply-To: <HK2PR06MB08171ADABF33A1DB0F55C5C9BBAD0@HK2PR06MB0817.apcprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [rZ27Em5j8rMx3KzXd6ugb10ncYpzzopv]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1;HE1EUR01HT091;7:ChfPFsQcPUInCDbt9l6mDt++rEaNeN3e/IFgal9R/3be+ShJKaHwWxJfovGEoFqA8TVdKDusTL6EZJrV7rEUqd/wT5yHRzzVA828pDD7s+2j3RCOjiBdYS0cNXW4jz/eroqA69EXtGRwiJIACJAlG4mN2bqYOPITIgQgZw6xh1lhsI7gU7fWkT3z46WO1Rjfp0HTZdw3aQIMs7TE/1Z4QypUWXTiX5hgeIXnA73+jPv3fCxKzaW/Ml7OMNK0/l0dlnAIlgqWSejuOmyQlvb/d1UKdXxRO59ajoXFrbwi+dNHSdTd0WstRQegZBrhvGttLJPuc+9lUzjvdsre2HdjcjhxuD87gTYa36FPTgBvejYqg29lUqD675YMKKBBxkUlD+0oKM5AoCWj70Nda8wB44pMAuH49LtfwNLflmgDX7MdfWHPP5UDqdnwKw0xLEPg12Zzs4JjliZedQLP/FRvoaB6kaOoVxMYeLHJevoc28xC7ZuSwEAJPTXDISD80FU5GlUt7CImB/mToiqar5NhXabGYiaFJmhTk8EyUPlhjvOyPMH4JUzg/RGJfhotwmUOAMMOEELpjoHSztjPHJEYa1uH8x5+l/0BI8ow3Rx6/WGH3Bwo6Ie5cJ11ikOgzZq1AA4c7sVjwYBO4BM88pCZYqtdr8sSytPjm2NEiMvzVp13nNDRfYlmMIiDzTXMM41ExuP4M3Xp3Q6G/2NbEPU1xeY+ynDhLsWUN4fnN8pIrnL5LNlNZHDYtV1Vqvf/c857gZZpWCp8YW41a0Hah1Ps/g==
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI;SFV:NSPM;SFS:(7070007)(98901004);DIR:OUT;SFP:1901;SCL:1;SRVR:HE1EUR01HT091;H:VI1PR0901MB0893.eurprd09.prod.outlook.com;FPR:;SPF:None;LANG:en;
x-ms-office365-filtering-correlation-id: 819e2a3e-d4ff-4000-082f-08d4cae67394
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095);SRVR:HE1EUR01HT091;
x-ms-traffictypediagnostic: HE1EUR01HT091:
x-exchange-antispam-report-test: UriScan:(43050042349365)(156600954879566)(236129657087228)(37052965297144)(90097320859284)(48057245064654)(25034144782879)(225559137633274)(50300203121483)(247924648384137);
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031);SRVR:HE1EUR01HT091;BCL:0;PCL:0;RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095);SRVR:HE1EUR01HT091;
x-forefront-prvs: 0368E78B5B
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_VI1PR0901MB0893C01265E776019914A4F0CDAD0VI1PR0901MB0893_"
MIME-Version: 1.0
X-OriginatorOrg: live.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jul 2017 18:30:49.5827
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR01HT091
archived-at: Fri, 14 Jul 2017 18:30:55 -0000

--_000_VI1PR0901MB0893C01265E776019914A4F0CDAD0VI1PR0901MB0893_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hello,


I imagine you are talking about Qpid Proton's reactor?

If that is the case, have you implemented the "onError" as well? Some error=
s go there.

Also, the reactor will always be running until you close the connection in =
one of the callbacks; are you doing so?

void on_transport_error(proton::transport &t) {
        t.connection().close();
}


Regards,
Adel

________________________________
From: Garlapati Sreeram Kumar <sreeramg@live.com>
Sent: Friday, July 14, 2017 6:39 PM
To: users@qpid.apache.org
Subject: RE: Reactor receiver stuck when transport is broken

Hello Folks!

Any help is much appreciated=85.

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=3D550986> for Window=
s 10
[http://www.microsoft.com/en-us/outlook-com/img/Outlook_Facebook_Icon-2927f=
4df28.jpg]<https://go.microsoft.com/fwlink/?LinkId=3D550986>

Check out Outlook.com =96 free, personal email from Microsoft.<https://go.m=
icrosoft.com/fwlink/?LinkId=3D550986>
go.microsoft.com
Find the right Outlook for you. Get the optimum email experience across all=
 your devices


From: Garlapati Sreeram Kumar<mailto:sreeramg@live.com>
Sent: Monday, July 10, 2017 5:09 PM
To: users@qpid.apache.org <mailto:users@qpid.apache.org>
Subject: Reactor receiver stuck when transport is broken

Hello folks!

We have a client with 1 Connection with 1 ReceiveLink running in 1 Thread w=
here it prints when ever onDelivery() handler is invoked.
Receiver sends flow for every 100 messages and Connection IdleTimeout on th=
e Service is 4 mins.

In some cases where there are transport issues =96 we noticed that neither =
onDelivery(event) nor onTransportError() are raised.
The receiver is stuck forever. Even the idleTimeout empty frame is logged a=
s written but, it is not detecting that the transport is broken. When we wo=
rkarounded this stuck receiver with creating another brand-new receiveLink =
on the same Connection =96 we then see onTransportError() event.
Is anyone experiencing this issue? Do, I have to actually listen for any ot=
her Transport events? Help is much appreciated=85

Thanks a lot for your Time!
Sreeram

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=3D550986> for Window=
s 10


--_000_VI1PR0901MB0893C01265E776019914A4F0CDAD0VI1PR0901MB0893_--