{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 我想做一个坏孩纸 的问题《Azure website keeps throwing the error “An attempt》','https://www.manongdao.com/q-614473.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I have a website running as a web app on a dedicated Azure plan. It connects to a Redis, SQL Azure and a MongoDB backend. The website has been running fine for weeks now and then without any new code I am now getting lots of socket exceptions starting like the one below.
An attempt was made to access a socket in a way forbidden by its access permissions.
The website intermittently gets the error when connecting to Redis, SQL Azure and MongoDB which makes no sense. I changed the Pricing Tier for the site which would move the website from one VM to another behind the scenes and the errors went away for a couple days and have returned again.
I just now changed the site from an S3 to an S2 (making it smaller) and they have gone away but I don't know for how long. How do I fix this? Does Azure limit the number of sockets for a site? Is there some setting on a site in Azure that could cause this?
Indeed, it does limit the amount of sockets. As far as I know, this isn't documented anywhere official. I do, however, have a blog post on this here: http://www.freekpaans.nl/2015/08/starving-outgoing-connections-on-windows-azure-web-sites/
I was getting the same error in the last few weeks. To fix that i deleted my website from azure and i redeployed using a different name. I know it is weird but when i deleted from azure and redeployed using the same name i got the same error again.