I am having a problem with my application displaying stale data which I believe is due to the 1st level Hibernate cache. I am using EJB3 with Hibernate 3.2.6. My app is also using SEAM extended persistence context by the way (not sure if that's getting in the way or not).

I have 2 browsers open with different sessions that display the same entity... Let's say it's some kind of an calendar event. Browser 1 edits the entity. I see the edits on browser 1 and the changes are committed to the database. Browser 2 has already loaded that calendar event entity in the session so it continues to pull it from the hibernate cache... even when I run a new query (this includes JPQL queries and load operations). If I refresh that entity explicitly or clear the persistence context I see the new data. I don't really feel I should have to do that though. Seems messy and problematic.

Is there a way to configure Hibernate to not pull the entities from the 1st level cache when running a query?

No one?