Yes if you are calling database queries directly you need to use the RetryPolicy explicitly. However retry policy is just hiding the problem (just enough to make it goes away). I strongly suggest to look into those "timeout issues" to figure out the root cause and fix it
Recently we are facing a lot of connection timeout issues with our application. So i want to use retry policy while connecting to commercemanager from my application. Can someone help with an example on how to leverage episerver SqlTransientErrorsRetryPolicy if i can. I hope its possible.
So far i've tried setting up below configurations in web.config.
<section name="episerver.dataStore" type="EPiServer.Data.Configuration.EPiServerDataStoreSection, EPiServer.Framework.AspNet" />
At the bottom inside configurations>
<dataSettings connectionStringName="EcfSqlConnection" retries="2" />
Here, EcfSqlConnection is my commercemanager connection string.
This gives me an issue launching api project.. Not sure if i'm heading in the right direction. Is there any seperate code change required as well.
Any help will be appreciated.