[rabbitmq-discuss] connections/queues hang using IE9 with web-stomp plugin

[Sebastien Dubois]

Hi,

  In our web application, we are using RabbitMQ with web-stomp to open 
websocket/sockJS channels to push notifications from the AMQP broker to the 
client browsers.

  When using IE9, the rabbitMQ connections are never closed when the client 
gets disconnected.  For example if the browser window/tab is closed, the 
connections/queues used during the session still appears as valid, even 
though they aren't.  This is potentially a big problem, as these "leaked" 
connection reduce the amount of available resources in rabbitMQ.  The only 
way to get rid of these invalid connections is to restart RabbitMQ, which 
is obviously unacceptable for a HA application like ours.

  I believe this might have something to do with the SockJS emulated 
websockets in IE9, as using a websocket-enabled browsers (e.g. IE10 or 11, 
Firefox, Chrome) works just fine (no leaked connections).

  Has anybody encountered this?  Is there a solution/workaround for this? 
 I know IE9 is getting quite old, but given our user base, we have to 
support it.

Thanks and BR,
/Sebastien
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140108/ecf2ad1c/attachment.html>