My application has about 20 threads (takes from pool).

This what I'm thinking about:

1) I use the ThreadLocalSession to associate a session with each thread.

2) I always keep the session open (or should I disconnect() after each RMI request ?) in order to make caching work

3) When the application ends, I have a finalizer in the ThreadLocalSession class that actually closes the session. Or will it close automatically?

Is this good or no good? It seems to work, but I'm not sure if it is the best approach.

My application has about 20 threads (takes from pool).

This what I'm thinking about:

1) I use the ThreadLocalSession to associate a session with each thread.

This is OK.

2) I always keep the session open (or should I disconnect() after each RMI request ?) in order to make caching work

It must be better to use JVM level cache, you dublicate cache per session and your caches are too isolated (session cache is local for transaction)


3) When the application ends, I have a finalizer in the ThreadLocalSession class that actually closes the session. Or will it close automatically?

Close it after transaction.

Think about session as connection wrapper and it must be clear how to manage it (if you know how to manage jdbc resources).

Thanks for the prompt reply.



How do I do that? Please elaborate.



But then session-level caching doesn't work???

I wan't my objects representing code tables to be cached between invocations. But if I close the session after the request, the cache is empty on the next call!

Thanks again.

Thanks for the prompt reply.



How do I do that? Please elaborate.

http://www.hibernate.org/hib_docs/refer ... ormance-s3



But then session-level caching doesn't work???

I wan't my objects representing code tables to be cached between invocations. But if I close the session after the request, the cache is empty on the next call!

Yes, it is vissible for single thread, multiple threads see different sessions and data in cache (I do not think you want this). Session level is good in transaction, transactions are isolated any way and no synchronization needed for this cache, it must be invalidated after transaction (or placed to the global cache).
As I understand you need global cache to reuse objects in multiple threads and looks like it is trasactional in hibernate.

Thanks again.