Connection takes ages to start after enabling feature/adding widget...

[François Camus]

First of all thank you for this module, I've been using it for a while and never had any issues.

I'm using Orchard 1.9.1 and the latest version of the master branch (2015-04-07).

The signalr connection takes a long time to start after I play a bit in the Orchard Dashboard. For example, if I add a widget onto a layer or enable a feature. I cannot navigate to another page while the connection hasn't started which is really annoying.

I can easily reproduce this issue with one of your samples: Benchmark. The "connected" label appears only once the connection has started. If you add any widget (HTML widget) onto a layer then navigate to the sample you'll see that the "connected" label takes ages to appear.

On IIS, once I recycle the app pool the connection starts quickly as before.

I'm not sure it comes from your module, SignalR 2.2.0 or Orchard 1.9.1.

I'm currently in an upgrade process (Orchard 1.9.1 and SignalR 2.2.0). I didn't have this issue with Orchard 1.8.1 and SignalR 2.0.2.

What do you think could be the cause?

Thanks in advance

[François Camus]

I'm still having the same issue by taking the Orchard 1.9.2 web deploy and your module.

I can even reproduce this issue by just editing a content in the admin. Weird...

[François Camus]

Alright it's nothing to do with your module. Cannot reproduce the issue when replacing the javascript file with 2.0.2 version. http://stackoverflow.com/questions/30075706/mvc-5-application-with-ajax-and-signalr-hangs-in-chrome

[François Camus]

SignalR bug

[François Camus]

Re-opening as discussed here: https://github.com/OrchardCMS/Orchard/issues/5975

[François Camus]

The issue comes from the swicth from using CoreRoutes to SignalrOwinMiddlewareProvider. In CoreRoutes you explictly specified that the routes SessionState was Disabled. I think the issue comes from that. I reverted your changes to re-use CoreRoutes and it fixes this issue.

[Kumar]

I am bitten by this bug as well. Could you please give more info on how exactly you overcome this issue? By the way, I am on Orchard 1.9.1.

[François Camus]

I did a diff between the latest version on this site and the one on the orchard gallery (1.3). You need to modify the latest version to reuse CoreRoutes as 1.3 did. Or find a way to disable SessionState within SignalrOwinMiddlewareProvider.

[Kumar]

It was very informative. I will check it out.

[François Camus]

I cannot reproduce this issue when web socket is supported. If I disable web socket in IIS then issue comes back.

[Kumar]

Despite with the fix you suggested? If so then I may have a solution found already.

[François Camus]

Check pull request #1. It should fix this issue. Tested in web socket and other modes.

[Piotr Szmyd]

Merged in FrancoisCamus/proligence.signalr-git (pull request #1)

Fixed issue #18

→ <<cset cd40cb8d2fb6>>