Last post Jul 16, 2019 01:46 PM by deepalgorithm
None
0 Points
6 Posts
Jul 16, 2019 06:41 AM|tonhei|LINK
We use signalr on scanners in a warehouse. There is a lot of loosing connections in a warehouse.
What we see that if signalr loses connections it keeps on building new connections.
We have more then a million signalr messages in iis log with 50 devices per day.
Any idea?
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=QNCbTmB8UWA57dtg59TcmA&_=1562889596005 80 - 172.18.100.202 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/58.0.3029.110+Safari/537.36+Edge/16.16299 http://10.48.27.147/sitemanager 200 0 0 5058 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=0a5pDc8uWJM-UCfCHPPLqw 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4978 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=4WIhpL9DBRCvd-FVC0l36g 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4856 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=1PFqYkvbJVWQLFo95JrFiA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4992 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=NGiaAzF75qA7ynHgrWvQQw 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4873 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=f8QHf4GAVhK0LpYNLT0N7w 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4995 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=c0r7D7mv9yvdfrrxdkQatw 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4872 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=KhjDTjTGEymiTa7T3UZsmQ 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4993 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=5UMylU1RRQfAp52be71OiA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 5001 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=Qh0ahVifGbewZDFxoWtbdQ 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4994 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=lCrcaXjmS5Q_VjkrWn-uSg 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4873 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=AUXPWGsiVjK8Kker3wNKXQ 80 - 172.17.228.145 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4317 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=yJqpCB8I2GOLpmiO2smjvg 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 5000 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=SDvDNyfRnTaU3SI1AvrVSA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4993 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=kZijNzdmYu_BUEeNPHuJDA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4992 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=vRqYwkuHj4rYFNSkd0hvnQ 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4872 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=lcIF6yp2xOH23MtLsyw2YA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4873 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=dwrPl9JgsPlYsd3i3D6-cw 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4992 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=bK7KsOgZmNfgD4YaaxinTA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4993 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=7BDwcEzIvR6f1KdsKkfgoQ 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4993 2019-07-12 00:00:00 99.99.27.147fGET /signalr/hub id=ucnp5I3k1ywsvg50T6PRfQ 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4999 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=NOSyWK499XmCguSqZ_Dd2g 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4872 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=6djm6fzsjyOTTvYdiOYd5g 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4873 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=j2W1IZjOLjOkryL9AMl45Q 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4993 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=IxuzPhGDcYvbV0rJkz1lcg 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4996 2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=BSo00oWwJxAG1EBby6BQJg 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4872
Participant
1190 Points
395 Posts
Jul 16, 2019 01:46 PM|deepalgorithm|LINK
Most likely, connections are timing out and disconnecting, so SignalR is creating new ones.
I'd read up on "Handling Connection Lifetime Events in SignalR"
https://docs.microsoft.com/en-us/aspnet/signalr/overview/guide-to-the-api/handling-connection-lifetime-events#terminology
None
0 Points
6 Posts
signalr keeps building connections
Jul 16, 2019 06:41 AM|tonhei|LINK
We use signalr on scanners in a warehouse. There is a lot of loosing connections in a warehouse.
What we see that if signalr loses connections it keeps on building new connections.
We have more then a million signalr messages in iis log with 50 devices per day.
Any idea?
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=QNCbTmB8UWA57dtg59TcmA&_=1562889596005 80 - 172.18.100.202 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/58.0.3029.110+Safari/537.36+Edge/16.16299 http://10.48.27.147/sitemanager 200 0 0 5058
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=0a5pDc8uWJM-UCfCHPPLqw 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4978
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=4WIhpL9DBRCvd-FVC0l36g 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4856
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=1PFqYkvbJVWQLFo95JrFiA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4992
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=NGiaAzF75qA7ynHgrWvQQw 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4873
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=f8QHf4GAVhK0LpYNLT0N7w 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4995
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=c0r7D7mv9yvdfrrxdkQatw 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4872
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=KhjDTjTGEymiTa7T3UZsmQ 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4993
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=5UMylU1RRQfAp52be71OiA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 5001
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=Qh0ahVifGbewZDFxoWtbdQ 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4994
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=lCrcaXjmS5Q_VjkrWn-uSg 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4873
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=AUXPWGsiVjK8Kker3wNKXQ 80 - 172.17.228.145 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4317
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=yJqpCB8I2GOLpmiO2smjvg 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 5000
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=SDvDNyfRnTaU3SI1AvrVSA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4993
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=kZijNzdmYu_BUEeNPHuJDA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4992
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=vRqYwkuHj4rYFNSkd0hvnQ 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4872
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=lcIF6yp2xOH23MtLsyw2YA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4873
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=dwrPl9JgsPlYsd3i3D6-cw 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4992
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=bK7KsOgZmNfgD4YaaxinTA 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4993
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=7BDwcEzIvR6f1KdsKkfgoQ 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4993
2019-07-12 00:00:00 99.99.27.147fGET /signalr/hub id=ucnp5I3k1ywsvg50T6PRfQ 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4999
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=NOSyWK499XmCguSqZ_Dd2g 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4872
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=6djm6fzsjyOTTvYdiOYd5g 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4873
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=j2W1IZjOLjOkryL9AMl45Q 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4993
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=IxuzPhGDcYvbV0rJkz1lcg 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4996
2019-07-12 00:00:00 99.99.27.147 GET /signalr/hub id=BSo00oWwJxAG1EBby6BQJg 80 - 172.17.228.158 Microsoft.AspNetCore.Http.Connections.Client/1.1.0-rtm-35687 - 200 0 0 4872
Participant
1190 Points
395 Posts
Re: signalr keeps building connections
Jul 16, 2019 01:46 PM|deepalgorithm|LINK
Most likely, connections are timing out and disconnecting, so SignalR is creating new ones.
I'd read up on "Handling Connection Lifetime Events in SignalR"
https://docs.microsoft.com/en-us/aspnet/signalr/overview/guide-to-the-api/handling-connection-lifetime-events#terminology