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

[Sebastien Dubois]

Hi again,

  I was finally able to make it work correctly by restricting SockJS to use
xdr-polling and xhr-polling for non websocket-capable browsers instead of
streaming that it was using.

Thx & BR,
/Sebastien


On Thu, Jan 9, 2014 at 12:24 PM, Sebastien Dubois <
dubois.sebastien66 at gmail.com> wrote:

> > Have you been able to determine which form of websocket emulation these
> connections use?
>
> From the IE9 traces, it does seems that we use xhr-streaming.
>
> > Have you checked whether the workaround in this issue helps?
> https://github.com/sockjs/sockjs-client/issues/54
>
> I'm not sure how to use this workaround.  As I understand, according to
> this info, we would need to change the way the SockJS sockets are createdon
> the server side, but isn't that done from within the web-stomp plugin
> itself?
>
> Thanks & BR,
> /Sebastien
>
>
>
> On Thu, Jan 9, 2014 at 6:10 AM, Emile Joubert <emile at rabbitmq.com> wrote:
>
>>
>> Hi Sebastien,
>>
>> On 08/01/14 17:43, Sebastien Dubois wrote:
>> > 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.
>>
>>
>> Have you been able to determine which form of websocket emulation these
>> connections use?
>>
>> Have you checked whether the workaround in this issue helps?
>> https://github.com/sockjs/sockjs-client/issues/54
>>
>>
>>
>> -Emile
>>
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140109/967182ea/attachment.html>