NHibernate + ASP.NET Identity + Autofac cache issue

Question

I'm building a profile page with update form. After submitting the form with new data and several page refreshes I see sometime new and sometimes old data. It depends on thread handling current request. One thread contains new data and another one old. NHibernate is configured using ThreadStaticSessionContext and NoCacheProvider. In Autofac UserStore, OwinContext.Authentication and UserManager are configured as InstancePerRequest.

I tried to change ThreadStaticSessionContext to CallSessionContext and it started working normally. So the question is: why it works(ThreadStaticSessionContext is preferable for multithread apps) and what negative effects can it bring?

Thanks!

is this a windows or web app?

Fran
– Fran

2016-08-19 15:06:27 +00:00
Commented Aug 19, 2016 at 15:06 — Fran
– Fran, Commented Aug 19, 2016 at 15:06
it's a web application.

SergB
– SergB

2016-08-22 13:04:51 +00:00
Commented Aug 22, 2016 at 13:04 — SergB
– SergB, Commented Aug 22, 2016 at 13:04

Community · Accepted Answer · 2017-05-23 12:23:00Z

0

ThreadStaticSessionContext is for long running processes such as windows services or windows apps. For web applications you want to be implementing Session Per Request. This is what the WebSessionContext is for.

I actually don't use any of the contexts and just wire it up myself. See my answer here for an example.

edited May 23, 2017 at 12:23

CommunityBot

11 silver badge

answered Aug 22, 2016 at 13:31

Fran

6,5801 gold badge26 silver badges37 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

NHibernate + ASP.NET Identity + Autofac cache issue

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related