Force refresh of collection JPA entityManager

by

You’re having two separate problems here. Let’s take the easy one first.

javax.ejb.EJBTransactionRolledbackException: Entity not managed

The List of objects returned by that query is not itself an Entity, and so you can’t .refresh it. In fact, that’s what the exception is complaining about. You’re asking the EntityManager to do something with an object that is simply not a known Entity.

If you want to .refresh a bunch of things, iterate through them and .refresh them individually.

Refreshing the list of ItemStatus

You’re interacting with Hibernate’s Session-level cache in a way that, from your question, you don’t expect. From the Hibernate docs:

For objects attached to a particular Session (i.e., in the scope of a
Session)… JVM identity for database identity is guaranteed by
Hibernate.

The impact of this on Query.getResultList() is that you do not necessarily get back the most up to date state of the database.

The Query you run is really getting a list of entity IDs that match that query. Any IDs that are already present in the Session cache are matched up to known entities, while any IDs that are not are populated based on database state. The previously known entities are not refreshed from the database at all.

What this means is that in the case where, between two executions of the Query from within the same transaction, some data has changed in the database for a particular known entity, the second Query would not pick up that change. It would, however, pick up a brand new ItemStatus instance (unless you were using a query cache, which I assume you’re not).

Long story short: With Hibernate, whenever you want to, within a single transaction, load an entity and then pick up additional changes to that entity from the database, you must explicitly .refresh(entity).

How you want to deal with this depends a bit on your use case. Two options I can think of off the bat:

  1. Have are to have the DAO tied to the lifespan of the transaction, and lazily initialize the List<ItemStatus>. Subsequent calls to DAO.refreshList iterate through the List and .refresh(status). If you also need newly added entities, you should run the Query and also refresh the known ItemStatus objects.
  2. Start a new transaction. Sounds like from your chat with @Perception though that that is not an option.

Some additional notes

There was discussion about using query hints. Here’s why they didn’t work:

org.hibernate.cacheable=false This would only be relevant if you were using a query cache, which is only recommended in very particular circumstances. Even if you were using it though, it wouldn’t affect your situation because the query cache contains object IDs, not data.

org.hibernate.cacheMode=REFRESH This is a directive to Hibernate’s second-level cache. If the second-level cache were turned on, AND you were issuing the two queries from different transactions, then you would have gotten stale data in the second query, and this directive would have resolved the problem. But if you’re in the same Session in the two queries, the second level cache would only come in to play to avoid database loading for entities that are new to this Session.

More Related Contents:

  1. Hibernate native query – char(3) column
  2. How to fix the Hibernate “object references an unsaved transient instance – save the transient instance before flushing” error
  3. How to map calculated properties with JPA and Hibernate
  4. How to fetch FetchType.LAZY associations with JPA and Hibernate in a Spring Controller
  5. When to use EntityManager.find() vs EntityManager.getReference() with JPA
  6. How to generate the JPA entity Metamodel?
  7. Hibernate: Automatically creating/updating the db tables based on entity classes
  8. How to use @Id with String Type in JPA / Hibernate?
  9. JPA Hibernate One-to-One relationship
  10. I found JPA, or alike, don’t encourage DAO pattern
  11. Hibernate – @ElementCollection – Strange delete/insert behavior
  12. Hibernate SessionFactory vs. JPA EntityManagerFactory
  13. Why does Hibernate disable INSERT batching when using an IDENTITY identifier generator
  14. JPA SQL Server No Dialect mapping for JDBC type: -9
  15. Deploying application using Hibernate JPA 2.1 to IBM WebSphere gives NullPointerException
  16. Can I combine a @Query definition with a Specification in a Spring Data JPA repository method?
  17. Multiple fetches with EAGER type in Hibernate with JPA
  18. Could not commit JPA transaction: Transaction marked as rollbackOnly
  19. Spring JpaRepository – Detach and Attach entity
  20. JPA Multiple Embedded fields
  21. JPA (Hibernate) and custom table prefixes
  22. java.lang.IllegalStateException: Multiple representations of the same entity with @ManyToMany 3 entities
  23. JPA: what is the proper pattern for iterating over large result sets?
  24. Create the perfect JPA entity [closed]
  25. Delete Not Working with JpaRepository
  26. Hibernate triggering constraint violations using orphanRemoval
  27. JPA: How do I specify the table name corresponding to a class at runtime?
  28. Spring, JPA, and Hibernate – how to increment a counter without concurrency issues
  29. Change Table Name of an Entity on runtime? [duplicate]
  30. How to map one class to different tables using hibernate/jpa annotations

Leave a Comment