Thanks for your reply I'm trying to understand the advantages of enabling producer control flow in broker's activemq.xml configuration file, when I use non-persistent delivery
Sorry, but I don't see any advantage, because I only can get a blocking in my producer. On the other hand, if I disable it , control flow is still managed by broker and messages for slow consumers are off-lined to disk storage Futhermore, I've read that non-persistent messages are persisted to disk ( feature from AMQ 5.x ) , so it's more difficult that memory runs out Which are advantages to enable producer control flow with non-persistent delivery ? If non-persisted message are persisted to disk ( by default ) , what is the advantage of non-persistent mode ? Thanks and regards 2013/12/9 Christian Posta <[email protected]>: > Yes, the protocol between the broker and client for sending/receiving > messages is still the same, ie, you would continue to get ACK messages > from the broker. > > If you set a producer window size, then byte counting/flow control is > handled at the client side for the default JMS openwire client. so you > would still experience throttling based on the client settings. > > > > On Mon, Dec 9, 2013 at 6:06 AM, Jose María Zaragoza > <[email protected]> wrote: >> Hi: >> >> I'm using AMQ 5.8 and I've got some basic questions about producer control >> flow >> >> - if I disable producerControlFlow in broker , does still producers >> receive ProducerAck messages/commands ? >> >> - if I disable producerControlFlow in broker, the producers who send >> persistent messages , does still they receive ProducerAck >> messages/commands? >> >> - if I disable producerControlFlow in broker and my producer sets >> window size ( setProducerWindowSize ), what is the behaviour ? >> >> >> Thanks and regards > > > > -- > Christian Posta > http://www.christianposta.com/blog > twitter: @christianposta
