Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC
Open Closed

Create User causing The wait operation timed out error #2253


User avatar
0
terry bentley created

I upgraded this past week to ASP.Net Zero v1.2 and when I create a user I am getting the following error

System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out

If I comment out the two lines await _notificationSubscriptionManager.SubscribeToAllAvailableNotificationsAsync(user.ToUserIdentifier()); await _appNotifier.WelcomeToTheApplicationAsync(user); in CreateUserAsync (UserAppService.cs) the user is created without a problem.

I am assuming there must be a deadlock in the database but I am not seeing any deadlocks in the SQL Profiler although I do see a reference to exec sp_executesql N'DELETE [dbo].[AbpNotifications] WHERE ([Id] = @0)',N'@0 uniqueidentifier',@0='1F3986A1-72E3-4CF2-A761-670629B6EF43' just before the first rollback.

This is a bit confusing as this is the notification record that is being added in the main transaction that has not been committed yet.

Any Ideas? Thanks... Terry


5 Answer(s)
  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi,

    What happens when you disable only one of those two lines ? Can you create a user in that case ? Or you must comment out those two lines together ?

    I'm asking because this is working in our project.

  • User Avatar
    0
    terry bentley created

    Sorry I should have checked this. It is the second line (_appNotifier.WelcomeToTheApplicationAsync(user)) that is causing the timeout. If I comment it out the user is added correctly but if I uncomment it fails.

    the second line (SubscribeToAllAvailableNotificationsAsync) is NOT a problem whether it is commented or not.

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi Terry Bentley,

    I couldn't repeat the problem. Can you send your project to us in order to check this problem ? If it is ok for you, please send it to <a href="mailto:[email protected]">[email protected]</a>.

    Thanks.

  • User Avatar
    0
    terry bentley created

    Thanks. I appreciate the offer but this project has developed into a high value proprietary system which we would not be comfortable releasing.

    For now, in the production copy, I have just commented out the "Welcome" notification call and will continue to investigate.

    One thing that would aid in the debugging is how do I have the debugger and log file look at my downloaded copy of the boilerplate and module-zero on my disk drive rather than
    D:\Halil\Github\aspnetboilerplate\src\Abp.EntityFramework\EntityFramework\AbpDbContext.cs:line 214

    Thanks again Terry

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi,

    As far as I know changing that log info is not possible. Directory name where the project is build is written in pdb files.

    You can build ABP in your machine but in that case someone else is going to see a path from your computer.