Hi guys, I have a problem with loading data from my database,sometimes hibernate loads half instead of all the data and when I refresh3 or 4 times, it gets fixed. Here is the case:

I have a link and by clicking on it the application should load list of all employees. When I run the application locally and try to load, everything is fine and I see list of all employees.BUT when I deploy the web application on the server and then try to load, sometimes I see only 3 or 4 rows of the employees while I have more than 30 in the database. Then I click 3-4 times to load again and then suddenly everything gets fixed! Can anyone help me on this?

I use hibernate 3,MySQL 5,Flex,BlazeDS.

Which Transaction Isolation Level are you using?

In case you are using READ COMMITTED then you must be aware of the fact,
that your application doesn't see uncommited data,
whilst maybe when you look at MySQL directly you may see uncommited data.

Another question: are you using some Hibernate 2lnd-Level cache implementation ?

Well I didn't set up the connection isolation property in my hibernate.cfg.xml so It should be in default mode. Should I set it?I can see the whole data in mysql. the problem is that on first click I may see the full list of employees on the sencond I may see the half of the list then on the third click again I may see the full list.
No I don't use any second level caching...

I suggest you log the jdbc activity with p6spy,
so you can see exactly which query is issued against the database and which result set is returned.

In this way you can see if it is the query to return wrong results,
or if it is somewhere else in the application where certain results are getting undermined.

I hibernate loading is working correctly... the problem is somewhere with fetching configuration... dont knowww :-((( thanks anyway.

Do you override the equals() and hashCode() of the employee entity?

N.B.: Wrong equals() and/or hashCode() implementations can easy lead to strange behavior.

ee ere chosea~~

No I didn't implement those functions... :-( should I implement them?

No, usually not.
Only in certain scenarios (i.e. when you intend to work with detached entities) it is necessary to implement them.