Hi all,

I am using Hibernate 3.2.5.ga and MySql 5.0 for building a web application.

In my web application I create an object of type 'User'.Each 'User' has around 4000 child objects of type 'WordInfo' associated with it.So a 'User' has a set of 'WordInfo'(s). I create a User in one session and retrieve its children WordInfo(s) back in another session using UserId(which is the primary key of User).

The issue I've been facing is quite random.I create a User 2-4 times and then access their children WordInfo in another session.Everything works fine.When I create more Users after this and then access their children,hibernate says no rows exist for WordInfo in the database.I get the following error..

INFO [03 Nov 2007 13:37:39,750] (DefaultLoadEventListener.java:111) - Error performing load command
org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.mywords.domain.WordInfo#202152]
at org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFactoryImpl.java:377)
at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:145)



But the WordInfo row with id #202152 does exist in the database.I dont know why hibernate says it does not exist?

Has anybody faced this issue before? Please help.

I haven't encountered such a problem yet but it sounds like an OutOfMemory-Bug.

Do you close/clear your session after you get the children objects for a user and before you get the next children objects for the next user? If not the reason might be that the number of persistent objects in the session increases with each query for the users children objects and is (at some point) too big.

Best Regards
Hoeft

thanks for your reply hoeft!

I do close my session after i retrieve child objects.Moreover I retrieve only 10-15 (pagination) child objects in one service call.

I just made changes to my hibernage.cfg.xml configuration file to not use Hibernate's internal pooling algorithm.Instead I'm using c3p0,an open source JDBC connection pool.That seems to have fixed the problem :) .I just read the hibernate documentation that says we should never use default connection pool provided by hibernate in production.That is intended only for development.