Databases
StackOverflow2013
Postsdbo
POSignalr: JavaScript client failing to reconnect on IE (parseerror exception)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSignalr: JavaScript client failing to reconnect on IE (parseerror exception)
    primarykey
    data
    text
    <p><strong>Configuration/Setup:</strong> </p> <ul> <li>Windows 7 64bit, .Net 4.5, Visual Studio 2012</li> <li>Self-Host Signalr Server (console app)</li> <li>JavaScript client</li> </ul> <p><strong>Background:</strong></p> <p>I started with <a href="http://www.asp.net/signalr/overview/getting-started/tutorial-signalr-self-host" rel="nofollow">this self host tutorial</a> as my base with the end goal of configuring a hub server that I can connect to across domains (CORS). I'm using mostly version 2.0.0-rc1.</p> <p><strong>Repo Steps:</strong></p> <p>The repo steps are easy. Navigate to the test page (default.html) from good 'ol IE (version 10) and wait.</p> <p>Here are the signalr client logs detailing what happens:</p> <pre><code>[21:47:30 PDT] SignalR: Auto detected cross domain url. [21:47:30 PDT] SignalR: Client subscribed to hub 'selfieserver'. [21:47:30 PDT] SignalR: Negotiating with 'http://localhost:8889/signalr/negotiate?connectionData=%5B%7B%22name%22%3A%22selfieserver%22%7D%5D&amp;clientProtocol=1.3'. [21:47:31 PDT] SignalR: Opening long polling request to 'http://localhost:8889/signalr/connect?transport=longPolling&amp;connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAAIkua2h4902EBFsaUr1NkAAAAAACAAAAAAADZgAAwAAAABAAAADId6sPY7u1b7U4MSyyjEGgAAAAAASAAACgAAAAEAAAAPbquY3AwSaeBDURBcXbiv8oAAAA5cpbDNk5rm0qDdq6nDWpqiazmTL4R%2Bv%2FI%2FSzcW1eAI71AkllpeDIKxQAAAAfYvObLT5lU2OeXpUvdjR%2B%2BLpotQ%3D%3D&amp;connectionData=%5B%7B%22name%22%3A%22selfieserver%22%7D%5D&amp;tid=8'. [21:47:31 PDT] SignalR: Long poll complete. [21:47:31 PDT] SignalR: LongPolling connected. [21:47:31 PDT] SignalR: Opening long polling request to 'http://localhost:8889/signalr/poll?transport=longPolling&amp;connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAAIkua2h4902EBFsaUr1NkAAAAAACAAAAAAADZgAAwAAAABAAAADId6sPY7u1b7U4MSyyjEGgAAAAAASAAACgAAAAEAAAAPbquY3AwSaeBDURBcXbiv8oAAAA5cpbDNk5rm0qDdq6nDWpqiazmTL4R%2Bv%2FI%2FSzcW1eAI71AkllpeDIKxQAAAAfYvObLT5lU2OeXpUvdjR%2B%2BLpotQ%3D%3D&amp;messageId=d-4213A9B0-B%2C0%7CU%2C0%7CV%2C1%7CW%2C0&amp;connectionData=%5B%7B%22name%22%3A%22selfieserver%22%7D%5D&amp;tid=4'. [21:48:01 PDT] SignalR: An error occurred using longPolling. Status = parsererror. Response = undefined. [21:48:04 PDT] SignalR: Opening long polling request to 'http://localhost:8889/signalr/reconnect?transport=longPolling&amp;connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAAIkua2h4902EBFsaUr1NkAAAAAACAAAAAAADZgAAwAAAABAAAADId6sPY7u1b7U4MSyyjEGgAAAAAASAAACgAAAAEAAAAPbquY3AwSaeBDURBcXbiv8oAAAA5cpbDNk5rm0qDdq6nDWpqiazmTL4R%2Bv%2FI%2FSzcW1eAI71AkllpeDIKxQAAAAfYvObLT5lU2OeXpUvdjR%2B%2BLpotQ%3D%3D&amp;messageId=d-4213A9B0-B%2C0%7CU%2C0%7CV%2C1%7CW%2C0&amp;connectionData=%5B%7B%22name%22%3A%22selfieserver%22%7D%5D&amp;tid=0'. [21:48:05 PDT] SignalR: Raising the reconnect event [21:48:35 PDT] SignalR: An error occurred using longPolling. Status = parsererror. Response = undefined. [21:48:38 PDT] SignalR: Opening long polling request to 'http://localhost:8889/signalr/reconnect?transport=longPolling&amp;connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAAIkua2h4902EBFsaUr1NkAAAAAACAAAAAAADZgAAwAAAABAAAADId6sPY7u1b7U4MSyyjEGgAAAAAASAAACgAAAAEAAAAPbquY3AwSaeBDURBcXbiv8oAAAA5cpbDNk5rm0qDdq6nDWpqiazmTL4R%2Bv%2FI%2FSzcW1eAI71AkllpeDIKxQAAAAfYvObLT5lU2OeXpUvdjR%2B%2BLpotQ%3D%3D&amp;messageId=d-4213A9B0-B%2C0%7CU%2C0%7CV%2C1%7CW%2C0&amp;connectionData=%5B%7B%22name%22%3A%22selfieserver%22%7D%5D&amp;tid=1'. [21:48:41 PDT] SignalR: Raising the reconnect event [21:49:08 PDT] SignalR: An error occurred using longPolling. Status = parsererror. Response = undefined. [21:49:11 PDT] SignalR: Opening long polling request to 'http://localhost:8889/signalr/reconnect?transport=longPolling&amp;connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAAIkua2h4902EBFsaUr1NkAAAAAACAAAAAAADZgAAwAAAABAAAADId6sPY7u1b7U4MSyyjEGgAAAAAASAAACgAAAAEAAAAPbquY3AwSaeBDURBcXbiv8oAAAA5cpbDNk5rm0qDdq6nDWpqiazmTL4R%2Bv%2FI%2FSzcW1eAI71AkllpeDIKxQAAAAfYvObLT5lU2OeXpUvdjR%2B%2BLpotQ%3D%3D&amp;messageId=d-4213A9B0-B%2C0%7CU%2C0%7CV%2C1%7CW%2C0&amp;connectionData=%5B%7B%22name%22%3A%22selfieserver%22%7D%5D&amp;tid=7'. [21:49:18 PDT] SignalR: Raising the reconnect event [21:49:42 PDT] SignalR: An error occurred using longPolling. Status = parsererror. Response = undefined. [21:49:45 PDT] SignalR: Opening long polling request to 'http://localhost:8889/signalr/reconnect?transport=longPolling&amp;connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAAIkua2h4902EBFsaUr1NkAAAAAACAAAAAAADZgAAwAAAABAAAADId6sPY7u1b7U4MSyyjEGgAAAAAASAAACgAAAAEAAAAPbquY3AwSaeBDURBcXbiv8oAAAA5cpbDNk5rm0qDdq6nDWpqiazmTL4R%2Bv%2FI%2FSzcW1eAI71AkllpeDIKxQAAAAfYvObLT5lU2OeXpUvdjR%2B%2BLpotQ%3D%3D&amp;messageId=d-4213A9B0-B%2C0%7CU%2C0%7CV%2C1%7CW%2C0&amp;connectionData=%5B%7B%22name%22%3A%22selfieserver%22%7D%5D&amp;tid=9'. [21:50:00 PDT] SignalR: Raising the reconnect event [21:50:15 PDT] SignalR: An error occurred using longPolling. Status = parsererror. Response = undefined. [21:50:18 PDT] SignalR: Opening long polling request to 'http://localhost:8889/signalr/reconnect?transport=longPolling&amp;connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAAIkua2h4902EBFsaUr1NkAAAAAACAAAAAAADZgAAwAAAABAAAADId6sPY7u1b7U4MSyyjEGgAAAAAASAAACgAAAAEAAAAPbquY3AwSaeBDURBcXbiv8oAAAA5cpbDNk5rm0qDdq6nDWpqiazmTL4R%2Bv%2FI%2FSzcW1eAI71AkllpeDIKxQAAAAfYvObLT5lU2OeXpUvdjR%2B%2BLpotQ%3D%3D&amp;messageId=d-4213A9B0-B%2C0%7CU%2C0%7CV%2C1%7CW%2C0&amp;connectionData=%5B%7B%22name%22%3A%22selfieserver%22%7D%5D&amp;tid=8'. [21:50:45 PDT] SignalR: Couldn't reconnect within the configured timeout (30000ms), disconnecting. [21:50:45 PDT] SignalR: Stopping connection. [21:50:45 PDT] SignalR: Aborted xhr requst. </code></pre> <p>You can see that errors keep occurring and the client keeps reconnecting until the re-connection fails.</p> <p>As a bonus, I've created a repro app that you can download from skydrive <a href="http://sdrv.ms/13mj2mP" rel="nofollow">here</a></p> <p>If anyone has some insight to my issue or can point me in the right direct, it would make my day.</p> <p><strong>[UPDATE]</strong> Of the 5 devs that have tried to reproduce via the included source code, zero have been able to reproduce. </p> <p>I'm assuming at this point my problem is specific to my machine (duh?). With this assumption, what environmental element could be causing the signalr/poll?transport=longPolling request to "abort"?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDrew
    1. USDrew
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSignalr: JavaScript client failing to reconnect on IE (parseerror exception)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSignalr: JavaScript client failing to reconnect on IE (parseerror exception)
      1. USuser2611614
      1. VTFavorite
    3. VO
      singulars
      1. POSignalr: JavaScript client failing to reconnect on IE (parseerror exception)
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you running any sort of anti-virus software at all? We've seen that cause issues in some cases with long running HTTP requests. In this case the long poll is failing because the response returned is not valid JSON (or blank), which obviously shouldn't happen but some layer between your browser & the server may be interfering.
      singulars
      1. POSignalr: JavaScript client failing to reconnect on IE (parseerror exception)
      1. USDamian Edwards
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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