This, I believe has been fixed in 5.9.0. I tested using the latest versions
and found this to be working correctly.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/setProducerWindowSize-inhibits-propagation-of-ResAllocEx-producer-stays-forever-blocked-once-it-blocs-tp3782
Can someone explain this please? This question was asked in 2011 and yet I
see a similar behaviour with ActiveMQ 5.10.0.
The producer never recovers after the ResourceAllocationException.
There is very little or no documentation related to Producer Window Size.
It would be really helpful to the com
Any suggestions/hints? Let me know what additional details I can provide.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/setProducerWindowSize-inhibits-propagation-of-ResAllocEx-producer-stays-forever-blocked-once-it-blocs-tp3782348p3807775.html
Sent from the ActiveMQ - Us
I've been experimenting with various flow control scenarios and all the
"standard" scenarios worked as expected (sync/async sends with
sendFailIfNoSpace set/not on the broker side) - I'm seeing
blocking/AllocationException/nothing in the client depending on the
scenario.
What I really want is what
