[rabbitmq-discuss] Web STOMP hangs after a while

Nikita Tsukanov keks9n at gmail.com
Sun Feb 9 12:49:57 GMT 2014

Oh, I figured it out.
1) We're using nginx to proxy websocket connections (we need HTTPS)
2) For some reason connections get leaked in that case (nginx bug? dunno)
3) cowboy by default allows only limited amount of connections

So after a while the number of opened connections reaches the limit and
then it hangs

Now I've applied https patches from
https://github.com/jshiell/rabbitmq-web-stomp (I hope it will be merged to
upstream) and web-stomp serves connections directly. No any leaks, works
like a charm.

Regards, Nikita

2014-02-09 13:34 GMT+04:00 Michael Klishin <michael.s.klishin at gmail.com>:

> 2014-02-09 13:05 GMT+04:00 Nikita Tsukanov <keks9n at gmail.com>:
>> in RabbitMQ log and then even stomp/info stops responding to HTTP
>> requests. It happens after several hours under load of about 100-150
>> connections.
>> RabbitMQ itself and regular STOMP (that one on port 61613) continue
>> working without any issues.
> Nikita,
> Thanks for reporting.
> Do you have a small script or something that reproduces the issue most of
> the time?
> --
> MK
> http://github.com/michaelklishin
> http://twitter.com/michaelklishin
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140209/bd585852/attachment.html>

More information about the rabbitmq-discuss mailing list