I am currently working on a project that uses JPA (Toplink, currently) for its perseverance. We are currently launching one application server, but for redundancy we would like to add a load balancer and another sever application (and possibly more as it grows).
Firstly, I ran into a JPA caching issue. Since the two processes will update the same database, the JPA cache returns the cached value rather than going to the database. I see how to disable this, and the database itself implements the cache level. Turns off the cache completely the way here? I see ways to tell JPA to always get from the database at the query level, but in a multi-server environment it seems like you always want this to happen.
Along with this specific question, I'm interested in anyone who has implemented a JPA solution with multiple application servers and what problems have occurred during implementation (and any suggestions you have).
Many thanks.
source
share