- Original Message -
> From: "Gordon Sim"
> To: users@qpid.apache.org
> Sent: Tuesday, February 20, 2018 3:36:37 PM
> Subject: Re: C++ Broker Performance with large messages
>
> On 20/02/18 16:51, andi welchlin wrote:
> > Hello all,
> >
> > I tested throughput of the Qpid C++ Broker (c
On 20/02/18 16:51, andi welchlin wrote:
Hello all,
I tested throughput of the Qpid C++ Broker (compiled as Release).
It was tested on a virtual machine with 15 GB RAM.
First I sent a 100 MB message into a persistent queue. From sender to
receiver it took 16 seconds for one message.
Afterwards
Please vote on this thread to release qpid-dispatch 1.0.1-rc1 as the
official 1.0.1.
The release can be found here:
https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.0.1-rc1/
The following defects were fixed in this release:
DISPATCH-874 - unable to load .json or .woff2 files from
I also couldn't install using only pip install.
http://qpid.2158936.n2.nabble.com/trouble-connecting-to-Azure-Service-Bus-from-OS-X-td7672153.html
I ended up installing the qpid proton libraries using macports, then I was
able to install using pip. However, I was still unable to use it because it
Hello all,
I tested throughput of the Qpid C++ Broker (compiled as Release).
It was tested on a virtual machine with 15 GB RAM.
First I sent a 100 MB message into a persistent queue. From sender to
receiver it took 16 seconds for one message.
Afterwards I sent a 300 MB message, this one took 12
Marcel,
I don't see anything that you are doing wrong in this case. I will
see if I can reproduce your result.
-Ted
On Tue, Feb 20, 2018 at 9:57 AM, Marcel Meulemans
wrote:
> I am experiencing a problem while using the dispatch router as a proxy to
> the artemis broker. I have done some invest
I am experiencing a problem while using the dispatch router as a proxy to
the artemis broker. I have done some investigation and it looks like the
dispatch router is not always forwarding link credit to the broker.
I have the following setup:
proton clients 0.9.0 (old, i know :p) <---> qdrouterd 1
Answers to your questions..
Could you please clarify whether you have seen "Gave up waiting"
warnings with synchronous or asynchronous recoverer?
- definitely when using synchronous but also pretty sure it was after I made
the context change to use asynchronous recovery also. I've been making
Dear Apache Enthusiast,
(You’re receiving this message because you’re subscribed to a user@ or
dev@ list of one or more Apache Software Foundation projects.)
We’re pleased to announce the upcoming ApacheCon [1] in Montréal,
September 24-27. This event is all about you — the Apache project com
Thanks for the info. I was able to get the acls defined via the REST API
Update. There were a few little quirks I ran into where the documentation
on the ACL page
(https://qpid.apache.org/releases/qpid-broker-j-7.0.1/book/Java-Broker-Security-AccessControlProviders.html#Java-Broker-Security-Acces
Hi Joshua,
A similar issue was raised a few weeks ago, you might find that thread
useful:
http://qpid.2158936.n2.nabble.com/Error-installing-python-qpid-proton-0-20-0-tp7672530p7672660.html
Unfortunately I'm no more able to test this on a Mac than Ken, so that
information is all I can offer! I th
Hi Bryan,
Could you please clarify whether you have seen "Gave up waiting"
warnings with synchronous or asynchronous recoverer?
Do you have full broker log with the warnings? Can you share it?
Did you connect consumers to DLQs whilst the VH messages were
asynchronously recovered?
Kind Regards,
Al
Hi,
Is it possible to install python qpid proton on a mac?
I ran "pip3 install python-qpid-proton" but failed with:
"/private/var/folders/f0/8mtk875s79jcgcy1l590z69mgn/T/pip-build-Er8aX6/python-qpid-proton/proton-c/src/proactor/epoll.c:48:10:
fatal error: 'sys/timerfd.h' file not found"
Is q
13 matches
Mail list logo
