The frame below would suggest that something is going wrong on the Event
Hub side of things, or at least that someone at microsoft would need to get
involved in order to debug further. I do think there is at least one bug on
the proton side here as this error message should really be displayed by
d
Rafael -
The trace was too long. The details are in PROTON-786. It looks like
something is occurring on the Azure Event Hub side, so I don't know if
there is a lingering issue w/ quid-proton as well.
On another note, when a disconnect happens, is it possible that
"pn_messenger_status" could ret
On Fri, Dec 19, 2014 at 7:50 PM, Jim Spring wrote:
>
> Greetings -
>
> I've written a test application that all it does asynchronously send
> messages to Azure EventHub using qpid proton. At the quid-proton level, I
> have set the outgoing window (for tracking messages sent) at various sizes,
> b
Hi all,
I'm using qpid transferring large messages, the message size is more than
120MB, it will cost over 250ms.
My IB is Mellanox ConnectX-3 56Gbps FDR HCA card, when I use qperf -m 120m
serverip??it said:
[root@node2 qpid-benchmark]# qperf -m 120m 192.168.1.1 tcp_lat
tcp_lat:
latency =
