You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My Abp application is deployed with IIS and nginx as the reverse proxy. The first few requests after the application started up had a werid problem that the request succeeded but the data was't saved to db. And the application logs said.
2025-01-08 15:54:25.704 +08:00 [ERR] An error occurred using a transaction.
2025-01-08 15:54:25.707 +08:00 [WRN] An exception occurred, but response has already started!
After a few times of faults, it turned to work and this is specific to appservices which means even if app services A became working fine, But app services A still did't work.
But if I direct request to iis, everything works fine.
I find a similar issue, but that issue has not much information.
Reproduction Steps
No response
Expected behavior
No response
Actual behavior
No response
Regression?
No response
Known Workarounds
No response
Version
8.1.1
User Interface
Common (Default)
Database Provider
EF Core (Default)
Tiered or separate authentication server
Tiered
Operation System
Windows (Default)
Other information
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Description
My Abp application is deployed with IIS and nginx as the reverse proxy. The first few requests after the application started up had a werid problem that the request succeeded but the data was't saved to db. And the application logs said.
After a few times of faults, it turned to work and this is specific to appservices which means even if app services A became working fine, But app services A still did't work.
But if I direct request to iis, everything works fine.
I find a similar issue, but that issue has not much information.
Reproduction Steps
No response
Expected behavior
No response
Actual behavior
No response
Regression?
No response
Known Workarounds
No response
Version
8.1.1
User Interface
Common (Default)
Database Provider
EF Core (Default)
Tiered or separate authentication server
Tiered
Operation System
Windows (Default)
Other information
No response
The text was updated successfully, but these errors were encountered: