1 of 1 people found this helpful
From a Hibernate Infinispan cache perspective, the biggest detail is achieved when TRACE is enabled on org.infinispan and org.hibernate.infinispan packages. You can try to run with DEBUG on this packages and see how the system behaves. That might gives us some clues on what's up, or at least a way to detect what goes wrong and be able to reproduce it outside a production environment.
If you want to go into more detail, I'd consider these the key packages to get an idea of what goes on:
In theory, CacheEntryInvalidatedEvent would be fired in the node where the data is removed as a result of an invalidation. However, since Hibernate 5.x we tweak internal Infinispan interceptors heavily to get best performance out of Hibernate Infinispan combo, so can't guarantee that listener will work as expected, but it should do.
Best here would be to get some logs when things go wrong and have a look.
In the mean, I'd suggest you:
1. Attach your Hibernate/JPA config and Infinispan config
2. Share the entity/collection classes that are having issues.
3. Does the issue affect entities only? Or collections only? Or both?
4. Are you using query caching? Is this affected by issue?
thank you for your reply. We've implemented some additional logging according to your advice and, for now, are waiting for something to happen.
Everything seems quiet so far, but should our issues resurface, I'll come back with additional information or a resolution.