Yes those settings are configured on the server side because it's the server that decides when to block. The broker is only going to throw an exception to the client if those settings have been enabled otherwise the client is just going to wait for space.
As you pointed out I think the only other thing you can do on the client side is that timeout setting, but you said are seeing it hang on close. It does seem weird to me that it would hang on that close request and not be able to process that so there could be a bug there. If you could submit a small unit test that shows the close hanging when the producer is blocked that would be great and someone could look into it to see if there is some improvement that could be done to fix that. Otherwise, when I get some time I can try and reproduce the issue and create the test case. On Mon, Apr 4, 2016 at 12:24 PM, Paulon <onei...@dnb.com> wrote: > Hey, > > are they not all configured on the MQ server side though? > > I don't have access to that as its on the Customer side (we are delivering > to them) > Is there anything that can be configured on the Producer side? > > Cheers! > Paul > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Force-Producer-to-fail-when-blocked-by-slow-consumer-tp4710264p4710339.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
