Is there any chance you could simplify the reproducer a bit (e.g. remove the ring queue configuration stuff and send to the address instead of directly to the FQQN)?
Justin On Fri, Nov 14, 2025 at 12:53 PM Patrick, Alton (US) <[email protected]> wrote: > Address-full-policy is "BLOCK." I'm attaching a broker.xml and a C++ app > that we use to recreate this problem. The program is invoked as: > > ProtonSender tcp://<IP>:<PORT> ring_static_block::ring_static_block_1000 > > That starts sending to the ring_static_block_1000 queue. Expect it to fill > up and then block the sender, but the actual behavior is as described in > last email. > > Thanks for any help. > > > -----Original Message----- > From: Justin Bertram <[email protected]> > Sent: Wednesday, November 12, 2025 6:02 PM > To: [email protected] > Subject: Re: Flow control with Artemis, AMQP, & Qpid Proton > > External Email Alert > > This email has been sent from an account outside of the BAE Systems > network. > > Please treat the email with caution, especially if you are requested to > click on a link, decrypt/open an attachment, or enable macros. For further > information on how to spot phishing, access “Cybersecurity OneSpace Page” > and report phishing by clicking the button “Report Phishing” on the Outlook > toolbar. > > > What's your address-full-policy? > > Do you have a test-case that demonstrates the issue which you can shared? > > > Justin > > On Wed, Nov 12, 2025 at 2:44 PM Patrick, Alton (US) < > [email protected]> wrote: > > > We are using an Artemis broker with clients that speak AMQP with the > > Qpid Proton library. We're trying to implement blocking on the > > producer as described here: > > > > https://activemq.apache.org/components/artemis/documentation/latest/fl > > ow-control.html#blocking-amqp-producers > > > > We have set both max-size-bytes and max-size-bytes-reject-threshold on > > the > > address: > > <max-size-bytes>1048576</max-size-bytes> > > > > <max-size-bytes-reject-threshold>524288</max-size-bytes-reject-thresho > > ld> > > > > What we expect to see: When the broker has received > > max-size-bytes-reject-threshold bytes of data, it should start > > rejecting messages. > > > > But we aren't seeing any messages get rejected. Instead, it continues > > accepting messages until max-size-bytes have been received. The > > message that pushes the buffer over that limit is dropped. After that, > > our producer stops getting credits from the broker and is effectively > > blocked. However, we do lose one message. > > > > I suppose we could add logic in the producer to figure out the message > > was dropped and retransmit it....but that doesn't seem like the way > > this is supposed to work. Is it? Are we doing something wrong? Has > > anyone successfully implemented blocking of AMQP producers with qpid > > proton without losing messages? > > > > -Alton > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact >
