Note that there are some explanatory texts on larger screens.

plurals
  1. POUnable to reconnect SignalR JS client after recycle of application pool
    primarykey
    data
    text
    <p>When i recycle my Application Pool for the site where the SignalR hub is running, the javascript clients is unable to reconnect. But everything is OK if the client do a refresh on his browser.</p> <p>In the clients console log, these lines repeat multiple times every second after a reset of the app pool: ( i have replaced the connection token with abcd )</p> <pre><code>LOGG: [15:51:19 UTC+0200] SignalR: Raising the reconnect event LOGG: [15:51:19 UTC+0200] SignalR: An error occurred using longPolling. Status = parsererror. undefined LOGG: [15:51:19 UTC+0200] SignalR: SignalR: Initializing long polling connection with server. LOGG: [15:51:19 UTC+0200] SignalR: Attempting to connect to 'http://lab/signalr/reconnect?transport=longPolling&amp;connectionToken=abcd' using longPolling. LOGG: [15:51:19 UTC+0200] SignalR: Raising the reconnect event </code></pre> <p>I have tried disabling all authentication on the hub, but still the same result. Both the server and client is running on SignalR v1.0.1</p> <p>The hubconnection on the client is set up like this:</p> <pre><code>var connection = $.hubConnection('http://lab:8097', { logging: true }); var proxy = connection.createHubProxy('task'); connection.start({ jsonp: true }).done(function () { proxy.invoke('OpenTask', id); }); </code></pre> <p>Im also using crossdomain on the server side hub registration:</p> <pre><code>RouteTable.Routes.MapHubs(new HubConfiguration { EnableCrossDomain = true }); </code></pre> <p>The server is running on IIS 7.5, and the client is IE9.</p> <p>Anyone have an idea what's wrong? </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload