Hi, "In ActiveMQ 4.x flow control was implemented using TCP flow control. The underlying network connection of throttled consumers was suspended to enforce flow control limits. This strategy is very efficient but can lead to deadlocks if there are multiple producers and consumers sharing the same connection."
(taken from http://activemq.apache.org/producer-flow-control.html) Could you describe more precisely flow control implemented and, especially, possible deadlocks? I am working on the problem described by Stefan: http://www.nabble.com/Conections%2C-sessions-and-threads-tf4513656s2354.html#a12873896 Notice: synchronous send() is used. I could easily reproduce the described case with ActiveMQ 4.1.1. But no problem is shown with 5.0.0. Could you refer to the changes made between the versions that could correlate with the problem. Thanks in advance, Matvey -- View this message in context: http://www.nabble.com/ActiveMQ-4.x-flow-control-tf4674212s2354.html#a13354432 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
