Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "Ricavir"

Hi @Ismcagdas,

I still have these warnings wit Abp 8.2.0. This should have been fixed, no ?

Answer

Hi @Ismcagdas,

No, API and app are hosted in the same server. The main point is how do you manage {TENANCY_NAME} in the URL when using a CDN endpoint.

So I found a ticket mentioning this issue here : https://support.aspnetzero.com/QA/Questions/10676/Impersonation-does-not-work-when-deployed-to-Azure-as-single-solution#answer-66330984-19de-b804-a427-3a003e99f3d1

The workarround is working

But why this happened ? Is there other impacts linked to this ?

Hi,

Here is the issue : https://github.com/aspnetzero/aspnet-zero-core/issues/4667

Hi

Thank you very much @Ismcagdas :)

Sorry @Ismcagdas, I just saw that Hangfire is able to manage background jobs on multiple instances. I will try it and come back to you if I need some additional help. This ticket can be closed.

Hi @Ismcagdas, thank you for your feedback.

Can you provide an SQL command to do this stuff ? Or something similar ?

Hi @Ismcagdas,

It has been a while since the last time :)

In fact, WEBSITE_INSTANCE_ID is an environment variable available on Azure App Service VM's. So, yes, I can read it.

My problem is that I want to store it somewhere outside the VM, this is why I need your help. I was thinking to store it in cache (I'm using Redis) or in Azure blob storage.

What is your advise about this ? Can I access cache or azure storage before setting Configuration.BackgroundJobs.IsJobExecutionEnabled ?

My goal is to activate background job execution only in the first instance ; the one that will start the app. Therefore, if a new instance is pushed in by Azure (automatic scale), the background job execution will not be started twice.

I confirm that the issue was coming from Azure SQL database DTU count. I upgraded DTU to a significant amount (from 20 to 200 DTU's). This allowed to run the migrations correctly wihtout timeout. Then, back to original DTU count (20) and everything is working fine.

I close this issue

Hum, I think that the fact of reaching maximum DTU during the migration is causing an abort of the process. I will try to switch to a premium tier with higher DTU count tonight. I will give you a feedback afterwords

Showing 11 to 20 of 232 entries