Do NHibernate sessions per thread work with threadpool?

Question

If I somehow manage to configure NHibernate sessions to be per thread, will that work when I process data in threads coming from a thread pool?

Threads from the pool are "recycled" (yes?) so if a thread was already used once and it gets called into action again, will its session be no loner useable?

Answer 1

The correct handling of the ISession is fully in your hands, you are responsible. Not the ThreadPool. So, if you use session instance per thread, you still should know (and manage) when it is created, and that it is explicitly closed and disposed.

If that ISession management is in place, do not worry about issues with a Thread pool. On the other hand, it also means, that opening and keeping a session in [ThreadStatic] field - is not correct:

• Will values in my ThreadStatic variables still be there when cycled via ThreadPool?

short extract:

The thread pool (by design) keeps the threads alive between calls. This means that the ThreadStatic variables will persist between calls to QueueUserWorkItem.