Hi,

I have the following use case:

I've some entity cofigured to use second level cache (ehcache is the provider). Is persisting a new instance of that entity will automatically update the cache with it (for future select using pk)?

A check I made says no - I saw that the first fetch after the persist still hit the db, and future fetches indeed got the entity from the cache.

Is this the expected behaviour or its possible to update cache along with the persisting?

Thanks.

I'm not sure but I'd say the cache does not contain that new entity and it will only be put into the cache if you execute a select query.
Thus the first query will hit the database and the entity will be put into the cache. If you'd only persist the entity but never read it again (or not in the "near" future) you'd not need it to reside in the cache.

This indeed suites my observations. Is there a way to put the entity in the cache manually?

If the entity contains references to other tables, they are obviously not loaded if you just persist this new instance.

Maybe this could also be one of the reasons.