Is there a way to
1 - Determine the size of the current First level cache so that when it hit's a threshold we can do a session.clear()?
2 - Change the behaviour through configuration so it does this automatically?

We find that we are blocking on this to much (Jprofile shows this in query.list() synchronizedMap block. Currently if we clear the cache after every query we are faster then letting it fill up.


Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version: 3.2

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using: Happens in both Oracle 10g and Sqlserver

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:


Problems with Session and transaction handling? Problem is

Read this: http://hibernate.org/42.html