System.OperationCanceledException at Microsoft.Extensions.Caching.Redis.RedisCache+<RefreshAsync>d__25.MoveNext about session

[Tratcher]

It's coming from here:

Session/src/Microsoft.AspNetCore.Session/SessionMiddleware.cs

Lines 115 to 122 in f633547

	try
	{
	await feature.Session.CommitAsync(context.RequestAborted);
	}
	catch (Exception ex)
	{
	_logger.ErrorClosingTheSession(ex);
	}

What's new in 2.0 is that IDistributedCache supports CancellationTokens, so Session passes the RequestAborted token. The effect of this is that if the client disconnects before the response is finished then their session changes are not persisted and you get this error logged.

We should consider special casing this exception type and downgrading the log level.

[amirjalali1]

@Tratcher
will it be available in version 2.0.1. and is there any release date for version 2.0.1 ?
is it really an error? and is there any solution for this issue?
i set log level to warning and above.
currently my log db has get so cluttered because of this error.

[Tratcher]

We haven't made any changes yet and have not decided if this should be included in any patches.

@muratg We've gotten several hits on this. Adjusting the logging may be appropriate for a patch.

[muratg]

@Tratcher agreed. @Eilon, patch candidate in 2.0. Idea is the to

1. Lower the log level, to Info
2. Change the message. Remove the stack trace and add a line mentioning client disconnect.