After adding level 2 cache hibernate is returning null for an entity. Hibernate returns null for the entity (TrackingItem) because it can't find a ManyToOne relationship (Navigation) in the cache. When it attempts to query the database for the Navigation the query returns 0 rows even though it exists in the database. Without level 2 cache hibernate is able to find the entity in the database.

Here's my environment:
Server: JBoss EAP 6.1
Hibernate 4.2.0.Final
Infinispan: 5.2.6.Final

I have a question out on stackoverflow (http://stackoverflow.com/questions/21417860/hibernate-unable-to-find-entity-in-the-database-after-adding-second-level-cache) regarding this issue with the full details. I'm posting this here in hopes a few more people see it and have some ideas on why Hibernate can't find the Navigation in the database and then returns null for the TrackingItem.

Any help would be appreciated.

Would you be willing to create an HHH JIRA ticket for this, including a runnable test case that shows what you're describing? https://hibernate.atlassian.net

Actually, in taking a quick look at this, you're using Dates/Calendars within your PKs. Generally, that is a really bad idea and can cause issues within core ORM itself. Adding in caching on top of that is worse. I'd highly recommend changing this up to use non-Date identifiers...