Pat,
Welcome to JavaRanch!
pat ker wrote:It was working good but as my application is multi-users, if someone else do another query on the same table at the same time, it seems the table is locked by the select/update.
This is a design problem and not a technology problem. If you really need to lock the whole table (or thousands of rows), you are going to have issues with multiple users regardless of whether using Hibernate or
JDBC. (A stored procedure might help as it would at least cut down on the network traffic on transferring thousands of rows.)
What is your application doing locally with those thousands of rows? Is it something that can be done on the database? Can the transaction be made shorter?