Should the session be flushed explicitly when using hibernate with second level cache in order to avoid constraint violation exceptions?
Issue
When using persistence via Hibernate/JPA API with second level cache on, would the order of operations be preserved or special care should be taken to avoid constraint violation exceptions?
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.