Closed ming-tsai closed 1 year ago
Hello @ming-tsai ,
Do you think you could create a runnable project with the issue? It doesn’t need to be your project, just a new solution with the minimum code to reproduce the issue.
We did some testing and didn't find any issues. The timeout we specified was always taken by either our library or EF Core when we directly used their method. For example: https://github.com/zzzprojects/EntityFrameworkExtras/blob/master/EntityFrameworkExtras.Shared/DatabaseExtensions.EFCore3x.cs#L109
If you can reproduce it, we will be happy to look at it.
In your stored procedure, you can simply use a WAITFOR DELAY '00:02:00';
to reproduce a stored procedure that take a lot of time to get executed.
Best Regards,
Jon
Sponsorship Help us improve this library
Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function
Yes, I have tested it, and actually, it works, but I don't know why in my project launch that exception, Let me make some changes, and I will let you know.
Sure, we will re-open this issue as soon as you can provide a project that reproduce it.
Here is what to include in your request to make sure we implement a solution as quickly as possible.
1. Description
Hi, Hope you are doing well, I just trying to using the ExecuteProcedureAsync but it launch the timeout exception in 1 minutes, however my dbcontext is configured in 30 minutes.
2. Exception
If you are seeing an exception, include the full exception details (message and stack trace).
3. Fiddle or Project
I couldn't add my project because is organization project, but I'm running the procedure using the BackgroundService and calling the method as below
4. Any further technical details
The procedure will take kind of 10~15 minutes dependes the data, and the package version I used is.