Open andrewmadueke opened 3 months ago
We are using azure sql without an issue. Some things to note:1. Depending on setup sql connections that are idle may timeout (we only use repositories within I singleton using work<> to overcome this - can be configured to use azure sql direct rather than through a gateway - it’s the gateway that times out the session)2. There is a mandatory request timeout at something like 15mins on http requests to the app service
Regards, Damon GroenveldOn
Let me also mention that we're not using the Orchard.sdf. We're reading the orchard settings from databases in a Sql Managed Instance and Sql Server on Prem. Thanks
There was a perf improvement in 1.10.3 for the query that is the issue in your logs, due to a SELECT n+1 problem, which could explain why it's timing out. You could try to apply this fix or move to 1.10.3.
The dev branch (1.11) also added some caching on top of this improvement, which is something you could also try, and would probably help a lot.
Check the DefaultLayerEvaluationService.PopulateActiveLayers
in both 1.10.3 tags and dev branch to see these two improvements.
I'll look into this Sebastien. Thanks for the quick reply.
Has anyone encountered similar issues? The exception below just started popping up out of nowhere after many years of using Orchard. The site gets locked and no one is able to navigate for periods of time. Would it help to upgrade Nhibernate to a newer version? Should I also look at upgrading orchard Framework to version 1.10.3? Moving to Orchard Core is out of question for now due to budget.
Current Orchard Framework Version: 1.10.2 Current Nhibernate version: 4.0.4.4000