If you want to simply build proton without the fuzz tests for whatever
reason you should just run cmake with the following option:
cmake ... -DENABLE_FUZZ_TESTING=OFF
or use ccmake to toggle that option. You have no need to patch the
source.
Having said that, we do test building proton on RHEL 6
By tripeling the number of JMS producers/consumers I could again max out the
CPU, however the messages rate is now still 40% lower than without having
failover enabled and fewer JMS producers/consumers.
The only reason I want to enabled the failover option is to have the qpid jms
client transpa
I am doing performance tests with Artemis 2.6.2 and QPID-JMS 0.34 client. I can
max-out the CPU of test machines (client and broker) with my qpid-jms based
performance client that uses multiple producers/consumers if I am configuring
the qpid client without failover. If I however change the conn
Hello,
It could also be a proxy issue 😉
I had it before when I was in my previous company and we were behind a proxy.
Regards,
Adel
From: Ken Giusti
Sent: Thursday, July 5, 2018 3:50 PM
To: users
Subject: Re: [Dispatch 1.2.0] Wrong download link in the web page
Hi Olivier,
When I tried going through the web page and did get a valid tar file.
Using the download link from that page redirects me to one of several
recommended mirror sites. Perhaps the mirror site you ended up on has a
corrupted file?
Can you let me know which mirror site you ended up on?
The link on the release page is to another web page which selects and
displays an appropriate mirror URL for you to download from and
provides some alternatives. Works fine here. Once the next release of
Dispatch is out, the link on the page will just point at the archive.
Robbie
On 5 July 2018 a
Hello,
When downloading the latest version of the dispatch-router from the web page:
https://qpid.apache.org/releases/qpid-dispatch-1.2.0/index.html
I get an artifact that I can't even untar... gzip: stdin: not in gzip format
Note that on the other hand I have no problems when downloading it fro
