- ABP Framework version: v9.X.X
- UI Type: MVC / Blazor WASM / Blazor Server
- Database System: EF Core (SQL Server
- Tiered (for MVC) or Auth Server Separated (for Angular): no
- Exception message and full stack trace:
- Steps to reproduce the issue:
Here’s the corrected version of your text:
We recently encountered a very strange bug. We updated the emailing settings with our own SMTP credentials, and it worked. However, this morning, the emailing feature stopped working.
I checked the emailing settings page using an admin account, and it showed the default credentials with the original settings, as if we had never changed them back to the original.
I then checked the database, and the AbpSettings table appeared correct—it contained all the correct SMTP information, which is very strange. So, I updated all the fields on the emailing settings page again, and it worked.
I'm concerned that the issue might return. Do you have any suggestions? how can I make sure that it will use the correct smtp?
3 Answer(s)
-
0
Hi, emailing settings are retrieved through the
ISettingManagerservice, which caches data internally. Most likely, the old values you saw were due to cached data.Now that you've updated the settings again, the cache should be invalidated, allowing the latest values from the database to be used and re-cached. You shouldn’t encounter this issue again.
Regards.
-
0
- after I updated it the first time, how did the cached data come back? since it worked for a while. I just wanted to understand it more so that we know how to deal with this cache issue.
- is there a way to delete all cached data and let it load data from the db again?
-
0
Hi, to be honest, it's weird to get a cache issue in your case. But it seems it was a temporary problem. If you reproduce it again we can deeper investigate it but probably it was a transient problem.
is there a way to delete all cached data and let it load data from the db again?
If you clear your cache, then the data will be loaded from db in the subsequent queries.
