Aspnetcore: DistrubutedSession error: A severe error occurred on the current command. The results, if any, should be discarded. Operation cancelled by user.

Created on 30 Aug 2018 · 16Comments · Source: dotnet/aspnetcore

I'm getting an error in DistributedSession. The source of the error seems to come from Cancellation tokens.
There was discussion on quieting some of the noisy logs coming from cancellation tokens here in Session Issue 189

I'm wondering if the same can be done for this error? Or, if not, how can I handle this error myself?

I'll keep trying, but so far, I'm unable to reproduce.

Exception Message: A severe error occurred on the current command. The results, if any, should be discarded. Operation cancelled by user.
Stack trace:

System.Data.SqlClient.SqlException (0x80131904): A severe error occurred on the current command.  The results, if any, should be discarded. Operation cancelled by user.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption)
   at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader(Boolean isInternal, Boolean forDescribeParameterEncryption)
   at System.Data.SqlClient.SqlCommand.InternalEndExecuteReader(IAsyncResult asyncResult, String endMethod, Boolean isInternal)
   at System.Data.SqlClient.SqlCommand.EndExecuteReaderInternal(IAsyncResult asyncResult)
   at System.Data.SqlClient.SqlCommand.EndExecuteReaderAsync(IAsyncResult asyncResult)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Extensions.Caching.SqlServer.DatabaseOperations.d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Extensions.Caching.SqlServer.DatabaseOperations.d__21.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Extensions.Caching.SqlServer.SqlServerCache.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Session.DistributedSession.d__32.MoveNext()

The IIS logs also show this message in addition to stack trace: _Session cache read exception_

I found a test that tests for this message, if that helps.

asp.net core 2.1
MVC site with DistributedSqlServerCache. Session is backed by SqlServer.

Done area-middleware bug feature-Session

Source

john-luke-laue

👍5

All 16 comments

What's the actual exception type?

Tratcher on 30 Aug 2018

@Tratcher I updated the stack trace in my previous post to include it.
But here it is again:
System.Data.SqlClient.SqlException (0x80131904): A severe error occurred on the current command. The results, if any, should be discarded. Operation cancelled by user.

john-luke-laue on 30 Aug 2018

Same issue in our environment.

ReVolly on 27 Oct 2018

👍1

Same issue also now appears in our environment after upgrading Microsoft.AspNetCore.Session from 2.0.2 to 2.1.1.

russelkrause on 5 Dec 2018

👍1

On review - stack trace is different in my case - any date scheduled to resolve this issue, or is there a work around? The error is filling our log files.

Error closing the session.
System.Data.SqlClient.SqlException (0x80131904): Operation cancelled by user.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader() at System.Data.SqlClient.SqlCommand.InternalEndExecuteReader(IAsyncResult asyncResult, String endMethod) at System.Data.SqlClient.SqlCommand.EndExecuteReaderInternal(IAsyncResult asyncResult) at System.Data.SqlClient.SqlCommand.EndExecuteReader(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Extensions.Caching.SqlServer.DatabaseOperations.d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Extensions.Caching.SqlServer.DatabaseOperations.d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Extensions.Caching.SqlServer.SqlServerCache.d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Session.DistributedSession.d__32.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Session.SessionMiddleware.d__9.MoveNext()
ClientConnectionId:81bfe738-81ad-4373-b91d-facfe5728c54

russelkrause on 18 Dec 2018

There was a related change where we downgraded the severity of this warning. https://github.com/aspnet/Session/issues/189

That said, we should remove RequestAborted from CommitAsync.
https://github.com/aspnet/Session/blob/9e4b6a5e4a8d4c789b627a37b0342dad45c87b6c/src/Microsoft.AspNetCore.Session/SessionMiddleware.cs#L117

Tratcher on 19 Dec 2018

Odd - I am still seeing the stack trace above reported at the ERROR level in "Microsoft.AspNetCore.Session" Version="2.1.1" though it was reported as included in 2.1.0-preview, or do I have this wrong?

russelkrause on 20 Dec 2018

It only downgraded OperationCanceledException, yours is a SqlException.

Tratcher on 20 Dec 2018

@Tratcher Do you still want to make the change to CommitAsync?

shirhatti on 11 Jan 2019

Yes

Tratcher on 11 Jan 2019

I've the same issue in our environment. Is there any way to avoid this exception at least temporary. An also, what is the initial reason of this issue?

FinkoAI on 2 Apr 2019

👍1

Same issue in our environment

phehr2 on 30 May 2019

We are currently also facing this error. Any idea what is causing this?

ail: Microsoft.AspNetCore.Session.SessionMiddleware[1]
      Error closing the session.
System.Data.SqlClient.SqlException (0x80131904): A severe error occurred on the current command.  The results, if any, should be discarded.
Operation cancelled by user.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader()
   at System.Data.SqlClient.SqlCommand.InternalEndExecuteReader(IAsyncResult asyncResult, String endMethod)
   at System.Data.SqlClient.SqlCommand.EndExecuteReaderInternal(IAsyncResult asyncResult)
   at System.Data.SqlClient.SqlCommand.EndExecuteReader(IAsyncResult asyncResult)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.Extensions.Caching.SqlServer.DatabaseOperations.GetCacheItemAsync(String key, Boolean includeValue, CancellationToken token)
   at Microsoft.Extensions.Caching.SqlServer.DatabaseOperations.RefreshCacheItemAsync(String key, CancellationToken token)
   at Microsoft.Extensions.Caching.SqlServer.SqlServerCache.RefreshAsync(String key, CancellationToken token)
   at Microsoft.AspNetCore.Session.DistributedSession.CommitAsync(CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)
ClientConnectionId:xxxxxxxxxxx
ClientConnectionId before routing:xxxxxxxxxx
Routing Destination:xxxxxx.xxxxxx.xxxxxxxxxx.worker.database.windows.net,11026

Thanks
Marc

marc-mueller on 3 Jul 2019

That usually means the client disconnected, causing the session commit to be aborted.

@anurse we do need to address this, it's causing a lot of unnecessary noise.

Tratcher on 3 Jul 2019

👍1

@Tratcher : we have the same exception as Marc has.
In our service we are using Distributed SQL Server Cache and there the entry in the cache table is missing because of this exception.
Correct me if I'm wrong but as I interpreted you answer, it looks we could ignore this exception. Does this now have an influence on the current session (session state not written) or does it not have any impact?

knoxi on 4 Jul 2019

Correct, if the user disconnects before their session is saved then it will not be saved. I've changed this in 3.0.0-preview8 to not check for user disconnects here.

One workaround is to call Session.CommitAsync in app code without RequestAborted.

Tratcher on 4 Jul 2019

Was this page helpful?

0 / 5 - 0 ratings