AbpSession.TenantId is not set when saving audit logs in background

Hi guys,

I’am having an intermittent issue where AbpSession.TenantId is not set, even thought that client is sending the correct TenantId per request.

code behind GetItem:

public async Task<AdDto> GetItem(GetAdInput input)
        {
            var culture = await _applicationLanguageRepository.GetCultureAsync(AbpSession.TenantId);

            var sessionId = Extensions.GetGuid(input.SessionId);

            var ad = await _adRepository.SingleOrDefaultAsync(input.AdId, sessionId, AbpSession.UserId, input.IsEdit, culture.TwoLetterISOLanguageName);

            if (ad == null)
            {
                throw new UserFriendlyException("There is no such an ad.");
            }

            if (ad.TenantId != AbpSession.TenantId && ad.TenantId.HasValue)
            {
                throw new UserFriendlyException("Tenant session is not valid.");
            }

            if (ad.Status == AdStatus.Active)
            {
                ad.Slug = ad.Title.GenerateSlug();
            }

            var adOutput = ad.MapTo<AdDto>();
}

As you can see in the image below that the first request for GetItem?AdId=1000021352&isEdit=false was succeed without error but the second request failed with the error Tenant session is not valid

Abp version: V4.0.0 Template base: .Net Framework

Thanks

[maliming]

This is indeed due to an error caused by RunInBackground. Of course this problem is not easy to find because it does not cause a task exception log.

The problem is in the class HttpContextTenantResolverCache. My understanding is that the background thread incorrectly sets the contents of httpContext.Items [CacheItemKey] Causes random problems that cannot read TenandId correctly.

https://github.com/aspnetboilerplate/aspnetboilerplate/blob/e0ded5d8702f389aa1f5947d3446f16aec845287/src/Abp.AspNetCore/AspNetCore/MultiTenancy/HttpContextTenantResolverCache.cs#L7

If someone can share specific details inside, I am very interested to learn. 🙂

[maliming]

@armory09 Sorry, I have reproduced the problem you have encountered, please wait a moment.