ill always be running until you close the connection in one
of the callbacks; are you doing so?
void on_transport_error(proton::transport ) {
t.connection().close();
}
Regards,
Adel
________
From: Garlapati Sreeram Kumar <sreer...@live.com>
Sent: Fr
Hello Folks!
Any help is much appreciated….
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: Garlapati Sreeram Kumar<mailto:sreer...@live.com>
Sent: Monday, July 10, 2017 5:09 PM
To: users@qpid.apache.org <mailto:users@qpid.apache.org>
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
Hello All!
I am from Microsoft Azure EventHubs team & our javaclient depends on proton-j
for Amqp.
We use Reactor API’s to implement the client and also have built a connection
Retry mechanism on top of this – which is running great! Recently, we ran into
a Memory leak of byte[]’s which are
Hello There!
We use Proton-j AMQP library and built a library atop
(https://github.com/Azure/azure-event-hubs-java) Proton-j Reactor.
While running our clients for long duration (like 2-3 days on a Windows x64
machine) we notice that Reactor thread dies with error
