[rabbitmq-discuss] publish msg in immediate mode and rabbitmq server's memory is pilling up

陈宇剑 lwice04 at gmail.com
Thu Nov 8 01:14:49 GMT 2012


thanks for replying.

2012/11/7 Matthias Radestock <matthias at rabbitmq.com>

> On 07/11/12 13:30, 陈宇剑 wrote:
>
>> i check out that  i use the rabbitmq 2.8.6.
>>
>
> Hmm, that should be fine.
>
> However, ...
>
> note that any 'mandatory'/'immediate' messages that cannot be
> routed/delivered are *returned to the sender*. If the sender is not
> draining those messages from the socket then they could easily pile up at
> the server, causing memory usage to creep up.
>


i will make some tests.

>
> As Simon said, 'immediate' is going away, so I recommend that you replace
> it with a per-queue message ttl (http://www.rabbitmq.com/ttl.**
> html#per-queue-message-ttl<http://www.rabbitmq.com/ttl.html#per-queue-message-ttl>)
> of 0, as previously suggested. Messages discarded that way will simply get
> dropped rather than returned.
>

and thank you for your advice,

>
> Regards,
>
> Matthias.
>



-- 
南京大学 软件学院 陈宇剑
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121108/7d4b8d26/attachment.htm>


More information about the rabbitmq-discuss mailing list