Session is closed!

Harchet · **Joined:** Wed Oct 20, 2010 3:18 am **Posts:** 3

Hi everyone

I'm using hibernate with eclipse helios to extract data from a MySQL database. I have done several querys with the same format, but when I do a specific query Hibernate throws a Hibernate exception and with System.out.println(e.getMessage()); I get this: Session is closed!

I have checked before doing the query if the session is open (System.out.println(HibernateUtil.getSessionFactory().getCurrentSession().isOpen());) and it seems to be ok... The exception is thrown when i do the query. This is the first time in the code i'm opening a session btw.

here is the code:

Quote:

{
Transaction tx=null;
try{
Session session = HibernateUtil.getSessionFactory().getCurrentSession();
tx=session.beginTransaction();
System.out.println(HibernateUtil.getSessionFactory().getCurrentSession().isOpen());
Query q = HibernateUtil.getSessionFactory().getCurrentSession().createQuery("SELECT r.name, count(log.time) as numeroClicks FROM MdlResource r ,MdlCourseModules cm ,MdlModules modu, MdlLog log WHERE modu.name = 'resource' AND cm.instance=r.id AND modu.id=cm.module AND cm.id=log.cmid AND cmid!=0 GROUP BY r.name ORDER BY r.name");
if(q.list().size()!=0){
tx.commit();
return q.list();
}
else{
tx.commit();
return null;
}
}catch(HibernateException e){
System.out.println(e.getMessage());
e.getStackTrace();
return null;
}

Thanks for helping :D

vishudeveloper · **Joined:** Wed Oct 20, 2010 12:06 pm **Posts:** 3

Harchet,

Please post the Stacktrace for the exception.

Harchet · **Joined:** Wed Oct 20, 2010 3:18 am **Posts:** 3

There is no stacktrace... that's the problem. Only prints "session is closed!" because I have add "System.out.println(e.getMessage());"
This function returns a null value, without a stacktrace...

nordborg · **Posted:** Thu Oct 21, 2010 4:05 am

Code:

if(q.list().size()!=0){
tx.commit();
return q.list();
}

I suspect this is the problematic part... First you are calling q.list().size() ...then tx.commit() ... then q.list() again. I suspect that the session get's closed when you call commit and that the exception happens on the second call to g.list().

Quote:

There is no stacktrace...

Yes, there is a stacktrace... call e.printStackTrace() in your exception handler and you will see it.

Harchet · **Joined:** Wed Oct 20, 2010 3:18 am **Posts:** 3

in the catch section i have added "e.printStackTrace()", you can check it, and there was no stacktrace, but doesn't matter thanks for helping me! :D