• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6734
  • Last Modified:

is it required to flush and clear hibernateTemplate?

Hi ,
I am using Hibernate and Spring. we are using getHibernateTemplate().find() in our DAOs. After the find() is called, do we have to explicitly call flush() and clear()? Will it lead to memory leak if we dont flush and clear?
1 Solution
flush() don't help, becaus it only synchronizes with the DB
clear() helps if you are loading to much data
you can use evict() instead of clear() for specific objects

It don't load to memory leaks but if you are loading to much data, you have to evict()/clear() so that the session-cache doesn't get too big.

Normaly the session is cleared when it will be closed and you don't have to clear it on you own.
cuttieveenzAuthor Commented:
actually the data consists of CLOB column data...hence it is very large and leads to memory leak
Then I would advice to iterate through the result and evict each result

Iterator iter = session.createQuery("from CatImpl as cat").iterate();
while(iter.hasNext() ) {
	Cat currentCat = (Cat) iter.next();

Open in new window

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

cuttieveenzAuthor Commented:
In my DAO code is as follows:

List emp = getHibernateTemplate().find("from Employee");
return emp;

Here emp is a list of objects which has CLOB data. I get a memory leak due to this clob in hibernate.

That's why i changed the code as follows:

List emp = getHibernateTemplate().find("from Employee");
return emp;

Will this help?
Again flush() is no help for you. It only writes the current status of the session in the DB. That is not what you want. The objects remain in the session after flushing().

Your solution only helps partially as after this line:
List emp = getHibernateTemplate().find("from Employee");

all is in the session cache. If that amount is to much it crashes in that line, you have to use my proposed solution.

Here the example for your need:

Iterator iter = session.createQuery("from Employee").iterate();
List emps = new ArrayList();
while( iter.hasNext() ) {
        Employee currentEmp = iter.next();
return emps;

Open in new window

Sathish David Kumar NArchitectCommented:
flush() is used for flush getHibernateTemplate() content u were used in  session factory creation
Just a side question, do you experience LazyInitializationException when you call to get associated objects from the Employee you queried for, like employee.getDepartment().getName() ? What I try to ask is: is the Hibernate Session closed right after each call to HibernateTemplate?

Are you using CMT or BMT?? I ask this because the solution to your problem really depends on how you define the demarcation of a transaction and of a Hibernate session.

As mahome suggested, the Hibernate Session object will cache the result of any queries and will clear the cache out automatically when it is closed. But when does a Hibernate Session close? As you use the class  HibernateTemplate from Spring and make a query, if you setting is not correct, you will find that the Hibernate Session will always close itself right after each call.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now