Re: default limits of qpid-c++ broker, dispatch router, or proton?

2020-07-10 Thread tomt
Thanks for the fast response. I spent a good part of the afternoon looking into the whole flow control system to understand better given what you had asked. I am using the Python client as my receivers and the C++ API as my senders who each synchronously send on their own threads as fast as possi

Re: default limits of qpid-c++ broker, dispatch router, or proton?

2020-07-10 Thread Gordon Sim
On 10/07/2020 4:03 pm, tomt wrote: Thanks for the fast response. I spent a good part of the afternoon looking into the whole flow control system to understand better given what you had asked. I am using the Python client as my receivers and the C++ API as my senders who each synchronously send

Re: default limits of qpid-c++ broker, dispatch router, or proton?

2020-07-10 Thread Robbie Gemmell
The behaviour is going to be dependent on how your components are actually configured, so it's hard to say specifics without more detail on how e.g your router and broker are actually configured to work together with the clients. Senders have no ability to control credit, it is granted by the rece

Re: default limits of qpid-c++ broker, dispatch router, or proton?

2020-07-10 Thread Robbie Gemmell
On Fri, 10 Jul 2020 at 16:54, Gordon Sim wrote: > > On 10/07/2020 4:03 pm, tomt wrote: > > Thanks for the fast response. I spent a good part of the afternoon looking > > into the whole flow control system to understand better given what you had > > asked. > > > > I am using the Python client as m

Re: default limits of qpid-c++ broker, dispatch router, or proton?

2020-07-10 Thread Gordon Sim
On 10/07/2020 4:58 pm, Robbie Gemmell wrote: When you have the router in between the broker and producer/consumer clients, then what happens will depend on how things have been set up to operate I had assumed you were testing with the broker *or* the router, but re-reading after this I see I a

Re: default limits of qpid-c++ broker, dispatch router, or proton?

2020-07-10 Thread tomt
MY configuration is that I have my receivers connecting to the router (through an Apache web server) via websockets. The topics they subscribe to live in the broker. I have link routing configured for this, so I am getting real flow control (based on what I read in the link above) -- Sent fr

Re: default limits of qpid-c++ broker, dispatch router, or proton?

2020-07-10 Thread Gordon Sim
On 10/07/2020 7:51 pm, tomt wrote: MY configuration is that I have my receivers connecting to the router (through an Apache web server) via websockets. The topics they subscribe to live in the broker. I have link routing configured for this, so I am getting real flow control (based on what I re

Re: default limits of qpid-c++ broker, dispatch router, or proton?

2020-07-10 Thread tomt
You're right about the Python client. We have a websocket client utility that connects to the apache webserver and then locally we have a port that opens that we connect the python client to that. I'll try the different combinations. Thanks -- Sent from: http://qpid.2158936.n2.nabble.com/Apac

Re: default limits of qpid-c++ broker, dispatch router, or proton?

2020-07-10 Thread Chuck Rolke
qpid-dispatch includes some tooling to help with AMQP operations in the router. https://github.com/apache/qpid-dispatch/tree/master/tools/scraper To get started use a single router with appropriate logging turned on. Then run your tests to generate logs: only a few hundred messages short uniq