Hello, thank you for your answer. We checked your github article but I am not sure if this milestone will FIX the issue related to "Sleeping" connections (mentioned before). I saw documentation related to Expired Tokens BUT NOT Sleeping connection.
Is the same issue ?
Thanks
Hello, any update about this ? Thank you
Hi, The issue described previously is related to AbpUserTokens. A lot of connections keep "Sleeping" Status after authenticating method request. Requested Information about version is Attached.
Asp Net Zero version is Old because we purchase recent version recently (we did not update yet)
We need to know if is possible to solve this issue with actual version or is neccessary to update. In this case which steps we have to consider.
Thank you
REQUESTED FILES: https://workdrive.zohoexternal.com/external/3ea5c291564043a4afc2537793dcfd109351d3cb893ec6ae08b4badcc40acaf3
El problema que se describe a continuación está generando caídas constantes en la plataforma, necesitamso por favor nos guíen en la solución. Como podemos abordar este problema de múltiples conexiones abiertas?
Se observan cada tanto muchisimos queries del estilo
/* Params ( @__ef_filter__p_0 BIT ,@__ef_filter__CurrentTenantId_1 INT ,@__p_0 BIGINT ) */
SELECT [a].[Id] ,[a].[ExpireDate] ,[a].[LoginProvider] ,[a].[Name] ,[a].[TenantId] ,[a].[UserId] ,[a].[Value] FROM [AbpUserTokens] AS [a] WHERE ( (@__ef_filter__p_0 = CAST(1 AS BIT)) OR ([a].[TenantId] = @__ef_filter__CurrentTenantId_1) ) AND ([a].[UserId] = @__p_0)
Estas conexiones quedan en sleeping pero con transaccion abierta.O sea no haciendo nada del lado del SQL pero con transaccion abierta.
Similar tambien con
( @p0 DATETIME2(7) ,@p1 NVARCHAR(128) ,@p2 NVARCHAR(128) ,@p3 INT ,@p4 BIGINT ,@p5 NVARCHAR(512) )
SET NOCOUNT ON;
INSERT INTO [AbpUserTokens] ( [ExpireDate] ,[LoginProvider] ,[Name] ,[TenantId] ,[UserId] ,[Value] ) VALUES ( @p0 ,@p1 ,@p2 ,@p3 ,@p4 ,@p5 );
SELECT [Id] FROM [AbpUserTokens] WHERE @@ROWCOUNT = 1 AND [Id] = scope_identity();
Pueden estar mas de 10 minutos en sleeping. Probablemente sea la transaccion con ese Nombre.Probablemente asignado por Entity Framework. De cualquier forma hay algun problema con el manejo de los AbpUserTokens.
