Hello,
I am trying to implement a solution to setup multiple instances of the tomcat running the same application (this is just to provide scalability in terms of putting more machines to support a legacy application). The application uses Hibernate for the OR-DBMS persistence. I have been told that there may data consistency issues in using this approach.
So here is what I am trying to do.

Setup one tomcat server running Application A (using hibernate to connect to the database (say B).
Setup another tomcat server running Application A (using hibernate to connect to same database.

I have been told that as Hibernate using Cache to synchronize with the database therefore there may be chance of data corruption when using two hibernate instances to connect to the same database.
I checked the serverside.com where I found a similar question asked but without any satisfactory response.
Please note that the application is highly mission critical and the data is extremely sensitive.
thanks
Ali

this may create data inconsistency but not only for hibernate . even if u are not using hibernate data inconsistency is a main bottle neck to developing efficient mission critical application . i think you can make use of powerful features in hibernate (like versioning and pesimistic locks ... ) for efficient data management