[rabbitmq-discuss] rabbitmq with one producer no consumer
ovidiudeac at gmail.com
Thu Jul 15 15:21:35 BST 2010
I think that rabbit should protect itself from getting in an
inconsistent state. It closes the connection with the producer but
doesn't accept other connections either
On Thu, Jul 15, 2010 at 4:29 PM, Davorin Rusevljan
<davorin.rusevljan at gmail.com> wrote:
> On Thu, Jul 15, 2010 at 3:19 PM, Robert Raschke <rtrlists at googlemail.com>
>> I think you should use some flow control. If your Rabbit has the memory
>> alerts turned on, then your producer can pick up the
>> channel.flow/active=false and stop sending until you get the active=true.
>> Otherwise your sending of persistent message will eventually make Rabbit
>> run out of resources.
> well, I think RabbitMQ server should have (and it probably does?) means to
> stop accepting messages from the producer before it enters the inconsistent
> and unrecoverable state. Because in many applications server can not expect
> to have cooperative and well behaved producers, and it should be able to
> survive such situations without going down.
> davorin rusevljan
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss