Why does Hibernate throw org.hibernate.exception.LockAcquisitionException?

According to your mapping, the sequence of operations should look like this:

Person p = DAO.findPerson(id);Car car = new Car();car.setPerson(p);DAO.saveOrUpdate(car);p.getCars().add(car);Car firstCar = p.getCars().get(0);firstCar.setPerson(null);p.getCars().remove(firstCar);if (p.officialCar.equals(firstCar)) {   p.officialCar = null;   p.officialCar.person = null;}DAO.delete(firstCar);

An update or a delete means acquiring an exclusive lock, even on READ_COMMITTED isolation level.

If another transaction wants to update the same row with the current running transaction (which already locked this row in question) you won't get a deadlock, but a lock acquisition timeout exception.

Since you got a deadlock, it means you acquire locks on multiple tables and the lock acquisitions are not properly ordered.

So, make sure that the service layer methods set the transaction boundaries, not the DAO methods. I see you declared the get and find methods to use SUPPORTED, meaning they will use a transaction only if one is currently started. I think you should use REQUIRED for those as well, but simply mark them as read-only = true.

So make sure the transaction aspect applies the transaction boundary on the "mymethod" and not on the DAO ones.

I have Cars -> (1 -n) places.And i have a foreign key in the table place (id_car). This foreign key dont have an index.When i add an index to this foreign key, my problem is resolved.

Refer to This Answer