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 unique transfer payloads Run scraper on log file(s) to generate a web page to be viewed with browser. You can then see credit starvation, if any, in the Connections section. Individual message transfers through the router and related settlements are presented multiple ways. There's a lot there; check it out. -Chuck ----- Original Message ----- > From: "tomt" <tt...@netapp.com> > To: users@qpid.apache.org > Sent: Friday, July 10, 2020 3:49:19 PM > Subject: Re: default limits of qpid-c++ broker, dispatch router, or proton? > > 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/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
