Activities of "-bitman"

Hello @musa.demir,

I am looking forward to the updated version.

Thank you!

Hello ANZ Team,

I am faced with the same issue as stated in this ticket. I sent via email a video recording on how I made the 1-to-Many relationship and I believe it is following the steps explained here but the same error message comes out when I try to run the front-end angular side of the project. I am dead on the water and unable to proceed because of this. I hope there is a workaround?

Thank you!

Thank you @maliming.

Hello @maliming,

Thank you for replying. Based on how we call the api do you think a short interval is the one causing the expiration? Or can you suggest which avenue I should be looking at in order to avoid this?

Thank you!

If it helps, we have written an Android and an iOS application that is used by around 500 users and it sends API requests to the backend every 30 seconds. It seems that the RefreshToken() is failing at some point but I am not 100% sure because it is intermittent.

Please advise. Thank you!

Hello Rickfrankel,

Thank you for your help. I will try your suggestion and hopefully will resolve my issues.

I appreciate it.

Thank you!

Hello ANZ Team,

Apologies for the late reply. We found out the root cause of the SignalR issue in our Azure app services. It was the ARR Affinity settings turned OFF. Once we turned it back ON, all 404 exceptions went away immediately. As per documentation about ARR Affinity...

Improve performance of your stateless app by turning Affinity Cookie off, stateful apps should keep this setting on for compatibility.

That being the case, I saw from the forum post that the API is stateless...

https://support.aspnetzero.com/QA/Questions/6075/Is-AspNetZero-API-stateless-for-angular-SPA-apps

I would like to ask if this is the case then why is the API throwing 404s when ARR Affinity is turned ON in azure? Am I missing something?

In addition to this, I found this post related to the issue.

https://stackoverflow.com/questions/56795602/signalr-core-is-arr-affinity-needed-when-web-sockets-are-enabled-and-the-azure

We are at Angular+Core 8.2 version of AspNetZero, if that helps.

Bottom line, we would want to avail of the load balancing feature of Azure by turning OFF ARR Affinity and at the same time still be able to capitalize on the SignalR feature that is already integrated in your solution.

Any advise would be appreciated.

Thank you!

I believe the issue is explained here.

https://docs.microsoft.com/en-us/aspnet/core/signalr/scale?view=aspnetcore-3.1

We don't want to turn on ARR Affinity because it will affect load balancing on the server farm. On the other hand, we cannot continue having thousands of 404 errors from SignalR.

Please advise.

I am also attaching here the initial error I get when refreshing my app.

Hello @maliming,

We also faced this same problem in our azure production environment. We get that 404 error code running signalR and we have multiple instances. We are getting thousands of 404 errors from it. We need to resolve this ASAP because we are in production and it is causing the servers to bug down during peak operations and we cannot afford a single minute of downtime. Please help. This is critical.

Btw we are on Angular + .NET Core v8.2

Thank you!