If your JVM is crashing, and it is because of memory issues, swapping to an ORM solution is unlikely to help. You would just be swapping from a cache implemented one way to a cache implemented another. In fact, I'd diagree with your architect friend - large result sets in an ORM solution will probably consume more resources than using straight JDBC.
Hibernate can be used in a cluster, presuming you use a clusterable second level cache implementation (which is outside the scope of Hibernate).
However, are you sure memory is the issue? Are you actually seeing OutOfMemoryErrors? Does your CPU activity spike before the outage?
Hi Siva, I believe the Resultset cache is stored in the memory so you are seeing a frequent outages. Why can't to try using oscache to cache the resultset in the disk rather than the memory? Oscache is a open source api used for caching any objects. we have done this in one of our application and the performance seems to be good.
Give a try.
Joined: May 02, 2004
Thanks for your inputs I will look into Oscache that info was pretty much helpful.
We are not facing out-of memory issue, Actually we are facing Memory allocation failure issue.
Where the JVM heap although has 500 MB of free memory, Memory allocation failure occurs when Continuous free memory units (Memory is divided into number of segments) is not available this happens as the object size is very large