{"action":"opened","issue":{"url":"https://api.github.com/repos/SignalR/SignalR/issues/4261","repository_url":"https://api.github.com/repos/SignalR/SignalR","labels_url":"https://api.github.com/repos/SignalR/SignalR/issues/4261/labels{/name}","comments_url":"https://api.github.com/repos/SignalR/SignalR/issues/4261/comments","events_url":"https://api.github.com/repos/SignalR/SignalR/issues/4261/events","html_url":"https://github.com/SignalR/SignalR/issues/4261","id":377934302,"node_id":"MDU6SXNzdWUzNzc5MzQzMDI=","number":4261,"title":"All websocket connections are reconnected unexpectedly","user":{"login":"vikas-idealconcepts","id":44812686,"node_id":"MDQ6VXNlcjQ0ODEyNjg2","avatar_url":"https://avatars0.githubusercontent.com/u/44812686?v=4","gravatar_id":"","url":"https://api.github.com/users/vikas-idealconcepts","html_url":"https://github.com/vikas-idealconcepts","followers_url":"https://api.github.com/users/vikas-idealconcepts/followers","following_url":"https://api.github.com/users/vikas-idealconcepts/following{/other_user}","gists_url":"https://api.github.com/users/vikas-idealconcepts/gists{/gist_id}","starred_url":"https://api.github.com/users/vikas-idealconcepts/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vikas-idealconcepts/subscriptions","organizations_url":"https://api.github.com/users/vikas-idealconcepts/orgs","repos_url":"https://api.github.com/users/vikas-idealconcepts/repos","events_url":"https://api.github.com/users/vikas-idealconcepts/events{/privacy}","received_events_url":"https://api.github.com/users/vikas-idealconcepts/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-06T16:41:50Z","updated_at":"2018-11-06T16:41:50Z","closed_at":null,"author_association":"NONE","body":"We have a asp.net website developed in .net 4.7.2 and signalr and is deployed in IIS. This website makes websocket connections using signalr from client browser (99% clients are using Chrome) to IIS. We generally have 200-300 clients working on this app on their browser at a time. Each client works for hours on our web application. So far, we never had any issue with these long lasting web socket connections for last several years. Starting last month, we have started to face a very strange issue on production server. Production server works for hours without any issue and then suddenly all 200-300 websocket connections disappear in IIS worker process. Then within 500ms-2s, new connections appear (with 'reconnect' in URL) in IIS web worker process for all clients and then in 1-3 seconds all websocket connections disappear again. This disappear-reappear cycle continues until I reset IIS. Once I reset IIS, this issue goes away and new websocket connections stay. Issue also goes away if I wait for 20-30 minutes. This issue is happening 1-3 times a day. Always happens in day time on week days when we have maximum traffic. Please note that other non-websocket connections in same  worker process are not effected at all.\r\n\r\n### Expected  behavior\r\nAll websocket connections should not disappear and reappear for  no apparent reason.\r\n\r\n### Actual behavior\r\nAll websocket connections disappear and reappear continuously for 20-30 minutes.\r\n\r\n### Steps to reproduce\r\nNot sure if this is reproducible in test environment or not. We have 200-300 websocket connections and connections are long lasting (like 1-5 hours). This happens all of a sudden for no apparent reason. \r\n"}}
{"actor":{"display_login":"vikas-idealconcepts"}}