Last post Jun 05, 2013 09:00 AM by burgenet
Jun 04, 2013 06:54 AM|burgenet|LINK
We are testing the use of SignalR in a web application (MVC) that we are currently developing; and have ran into a rather odd issue. During development, testing was done with
an IPad version 5.1.1 and everything seemed to be running fine. However, QA tested using a newer IPad version (6.1.X) and have ran into some roadblocks... they later tested and also reproduced on IPad 3.
When the application launches it instantiates a SignalR connection in order to receive push notifications for various events. This ideally will remain active the entire browser
session. The problem is when the user tries to click a link to load a PDF file. This should open the pdf file in a new browser tab and it works properly for IPad version 5.1.1. However, on the newer IPad version 6.1, the tab opens but never loads and just
remains in a loading state indefinetely or until you close the tab with SignalR running. Once SignalR is closed, the new tab does load.
I've actually been able to Stop the SignalR service just before launching the new tab (window.open) and then immediately restart SignalR service - and this does correct the issue.
It seems as though on that particular IPad version, SignalR is consuming all of the available connections and any other requests are stalling.
We are curious if any other IPad version 6.1.X ( or 3) users have experienced any similar issues or if any can confirm that they are running without issue.
Thank you for any information that can be offered.
Jun 05, 2013 08:49 AM|tmorton|LINK
Your question would get more visibility if posted in the SignalR forum (http://forums.asp.net/1254.aspx/1?ASP+NET+SignalR). Is it OK for the moderation team to move it?
Jun 05, 2013 09:00 AM|burgenet|LINK
I have no issues with that. As an aside, we have tracked down one concurrency issue that was the result of a locked session in the MVC Application. We've not been able to test so far whether this will have any impact on the IPad issues. I'm highly doubtful
it will, but am hopeful it may solve the issue.
Once we are able to test, I will update with the results. -- (update: Unfortunately this had no affect)