[rabbitmq-discuss] 回复: No timeout and sockets not closed forStomp

zane 37714275 at qq.com
Mon Jun 30 07:19:21 BST 2014

My OS:
[www at 10-9-15-42 ~]$ uname -a
Linux 10-9-15-42 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux‍

we use stomp plugin for send message between users. we didn't configure queues. our business is on line transaction.
our connections are increasing, but we know that connections should not be so high in morning. and we found no timeout
for connections. so can you tell me how the timeout be configured OS-wide? thanks lot.

------------------ 原始邮件 ------------------
发件人: "Michael Klishin";<mklishin at gopivotal.com>;
发送时间: 2014年6月30日(星期一) 中午1:22
收件人: "zane"<37714275 at qq.com>; "Legacy list about RabbitMQ"<rabbitmq-discuss at lists.rabbitmq.com>; 

主题: Re: [rabbitmq-discuss] No timeout and sockets not closed forStomp

 On 30 June 2014 at 07:28:03, zane (37714275 at qq.com) wrote:
> > we use stomp plugin. when we have many users to sub/pub. we found  
> the sockets not closed.
> and no timeout. our socket descriptors will be full after sometime.  
> so can you help me?

Can you be more specific about what exactly happens?

Detecting unreachable peer with TCP can take a while and the timeout
can be configured OS-wide.

Staff Software Engineer, Pivotal/RabbitMQ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140630/d4087aa2/attachment.html>

More information about the rabbitmq-discuss mailing list