Yes, I forgot to mention that but I've been running with
-Djavax.net.debug=ssl:handshake:verbose and sometimes -Djavax.net.debug=all.
I think I have a strong theory of what the culprit might be. I found this
post:
http://qpid.2158936.n2.nabble.com/One-SSL-SASL-EXTERNAL-queue-creation-works-with-qp
On 24/02/2021 16:16, Petrenko, Vadim wrote:
Hi all,
I would like to understand better how Link routing works.
I have a Java Qpid JMS client, a Qpid router mesh (4 interior routers + 2 edge)
and two Artemis brokers on the other side of the mesh.
I define link routing in the Interior routers usi
Hi all,
I would like to understand better how Link routing works.
I have a Java Qpid JMS client, a Qpid router mesh (4 interior routers + 2 edge)
and two Artemis brokers on the other side of the mesh.
I define link routing in the Interior routers using a prefix (so it's not
address specific, to
With large buffers -- like 4 K -- putting the router in between two iperfs
on the 40 Gbit/sec link really does improve upon an iperf-only test.
I confirmed my suspicion/memory -- the reason is, in the iperf-only test,
the receiver goes to 99.7% -- 100.0% CPU. It hits 100% frequently. And it
is si
