Hello to all!

I´m developing some kind of social network using Hibernate´s reverse engineering.
It´s also my first experience with Hibernate so you can imagine the headaches i´ve had.

Well, i´ve been working for 3 months and now i have it workin' but not at %100.
I have two problems and i would appreciate very much any help or advice.

1 - When i lift up the server sometimes some tables are locked, but i can´t find out the reason.
Sometimes is one table, sometimes is another. It´s not the code (or at least i think so) because i recompile and
refresh and the table that wasn´t working works, but another doesn´t.
I´m getting:
Could not insert in X
Lockwait Timeout excedeed

This is driving me mad!!!!!

2 - Sometimes im getting different data for the same stimulus.
I´m using <property name="hibernate.connection.isolation">2</property> since i had this problem.
Also i generated th Equals and hashcode using GETTERS for the id´s. I had to do this because equals by id (and not getId())
was malfunctioning. I think this happened because the ids weren´t initialiazed, so using getters (ergo lazy-loading... am i right?)
was a solution.
But it still happens sometimes!!!!!!!!!!


ANY help or advice would be really really appreciated.
Thank you all and sorry to bother.

Just letting you know that im still having these problems and im running out of time!

The "monster" problem is the one that locks the tables.
If i restart the server the problem goes away. But this is no solution for production.

Please i need any ideas.
What may be causing this?

Help! I need somebody´s help!

I just wanted to thank you all for expert help.

I know Hibernate its a great framework, but i know now that its community its not that great.

Thanks again.

Hello

I dont know whether you got the solution by now or not. Are you trying to do any simultaneous operation on Database.
Normally timeout happens and table gets lock when we try to do 2 transaction at a time.
Second transaction waits for the first to finish its operation in DB and it waits till the first transaction releases the lock. So if in case the second transaction has to wait for longer period say more than time out period, it gives this error message.