In my web application I have a job executing a lot of write queries. This job must run very quickly and this is why I'm using **stateless sessions**.

Thus, as soon as I must update or insert an entity I'm using this **statless session**.

However, to retrieve the data used in my job I'm using a normal session (the one created by **Play Framework**), so that relationships are loaded.

This is usually working fine because I retrieve the data at the beginning of the job using the normal session, and then I update and insert changes using a stateless session (thus there is no conflict between the 2 sessions).

But, I'm now having an issue with this solution. I have an entity that I'm also updating from another job. And in my first job I need the last update of this entity (I need this entity to be synchronized between my jobs). Therefore, when I need it, I retrieve it using a new *SELECT* query, but the entity does not contain the last update! 

I assume it's because of the cache. When this entity is updated in another job using a stateless session, the normal session's cache is not updated and then when I execute my *SELECT* query to retrieve the last update, I just get what was in the cache (which is not the last update).

So, to solve my issue I would like to know if it's possible to execute a *SELECT* query with Hibernate, without using the cache. Actually I would like to force Hibernate to execute a new real *SELECT* query not using the cache to retrieve the last update from the database.

Do you have any idea?

**EDIT**

I'm using JPA