31 AM
To: users@qpid.apache.org <mailto:users@qpid.apache.org>
Subject: Re: Reactor receiver stuck when transport is broken
Hello,
I imagine you are talking about Qpid Proton's reactor?
If that is the case, have you implemented the "onError" as well? Some errors go
there.
Also, the reactor w
port_error(proton::transport ) {
t.connection().close();
}
Regards,
Adel
From: Garlapati Sreeram Kumar <sreer...@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
;
Subject: Reactor receiver stuck when transport is broken
Hello folks!
We have a client with 1 Connection with 1 ReceiveLink running in 1 Thread where
it prints when ever onDelivery() handler is invoked.
Receiver sends flow for every 100 messages and Connection IdleTimeout on the
Service is 4 mins.
I
Hello folks!
We have a client with 1 Connection with 1 ReceiveLink running in 1 Thread where
it prints when ever onDelivery() handler is invoked.
Receiver sends flow for every 100 messages and Connection IdleTimeout on the
Service is 4 mins.
In some cases where there are transport issues – we