[DDC-1846] Pessimistic lock does not retreive latest version of entity when entity is already in doctrine cache Created: 30/May/12  Updated: 23/Jan/14  Resolved: 07/Jul/12

Status: Resolved
Project: Doctrine 2 - ORM
Component/s: ORM
Affects Version/s: Git Master
Fix Version/s: 2.2.3
Security Level: All

Type: Bug Priority: Major
Reporter: Bram Klein Gunnewiek Assignee: Benjamin Eberlei
Resolution: Fixed Votes: 0
Labels: None

Mysql 5.5.22-0ubuntu1

Issue Links:
relates to DDC-2929 Pessimistic lock on Query does not up... Open


When setting a pessimistic lock on an entity (e.g. a row lock) and retreiving an entity from the database, Doctrine returns the entity from cache if it has any. When updating a counter on an entity for example, it is important the row is locked, retreived, updated and then unlocked to guarantee the counter keeps in sync. Using $em->clear(); before $em->find(); is a work-around for this problem, but as requested by Benjamin Eberlei on the google groups thread (https://groups.google.com/forum/?fromgroups#!topic/doctrine-user/N8Xop2-XbTY) this bugreport is made to fix this without the need of clear().

In the next example, if the entity is previously retreived already, find() returns that version instead of retreiving the current version from the database after the rowlock is set. When $em->clear(); can be used to work-around the problem

// $em instanceof EntityManager

//$em->clear(); // Uncommenting this fixed the problem

try {
	$entity = $em->find('Entity', $id, LockMode::PESSIMISTIC_WRITE);
	/* Update some fields, for example, decrease a counter */
	$entity->setCounter($entity->getCounter() - 1);
} catch ( \Exception $ex ) {

Comment by Bram Klein Gunnewiek [ 22/Jun/12 ]

Any update or ETA on this one? The work-around is still in my production code and I would like to get it out to get it cleaned-up a bit.

Comment by Benjamin Eberlei [ 04/Jul/12 ]

Why does the $this->_em->lock() in EntityRepository#find() don't work for you? It should grab the entity from cache, then do a SELECT 1 FROM table and do the pessemistic write lock on the row.

Comment by Bram Klein Gunnewiek [ 05/Jul/12 ]

I don't exactly know why that does not work. I created this bugreport on your request (see: https://groups.google.com/forum/?fromgroups#!topic/doctrine-user/N8Xop2-XbTY) because I couldnt figure out what I was doïng wrong.

The script that updates the entity is a long running console script, allot of times the entity in question is already in the cache and did not get locked properly. There are two seperate processes that work on the same entity (processing jobs from a jobqueu) and when updating the counters at the same time, and both scripts (with the same locking code as described in the bugreport) have to update a counter, the counter is not updated properly (e.g. both scripts do for example 2-1 where the first script should do 2-1, the second script 1-1 since the counter is updated by the first script).

Comment by Benjamin Eberlei [ 05/Jul/12 ]

Can you paste the SQL log that gets executed?

Comment by Bram Klein Gunnewiek [ 05/Jul/12 ]

Allright, I reverted the code back to my original code. Doctrine is updated to the latest dev version. Code looks like this:

$em = $this->getEntityManager();
#$em->clear(); // This fixes the locking problem

try {
    // Lock entity in db and load it to update counters
    $entity = $em->find($this->getEntityName(), $this->getEppEntityId(), LockMode::PESSIMISTIC_WRITE);

    printf('Decreasing pendingjobs with 1. Current amount of pending jobs is %d', $entity->getPendingJobs());

    $entity->setPendingJobs($entity->getPendingJobs() - 1);

} catch ( \Exception $ex ) {

The output of the debug statement looks like this (e.g. each line is printed by a different process. Instead of the first script decreasing 2 to 1 and the second script decreasing 1 to 0, both scripts decrease 2 to 1):

[2012-07-05 11:31:08] Decreasing pendingjobs with 1. Current amount of pending jobs is 2
[2012-07-05 11:31:07] Decreasing pendingjobs with 1. Current amount of pending jobs is 2

I enabled SQL logging but the thing is huge and I dont really know where to look. There is data in it that I dont want publically availible on the internet, is it possible to mail the to you directly?

Comment by Benjamin Eberlei [ 07/Jul/12 ]


Comment by Renaud Drousies [ 21/Jan/14 ]

Sorry to comment on a closed ticket, but this is also happening when setting a pessimistic lock on Query objects (unless you set the Query::HINT_REFRESH hint)


        try {
            $bar = $em->createQuery('SELECT b FROM Foo:Bar b WHERE b.id = :id')
                        ->setParameter('id', 150)
            var_dump($bar->getAmount()); // Yields some positive value
            $bar = $em->createQuery('SELECT b FROM Foo:Bar b WHERE b.id = :id')
                        ->setParameter('id', 150)
                        // ->setHint(\Doctrine\ORM\Query::HINT_REFRESH, true)
            var_dump($bar->getAmount()); // Yields 0

        } catch (\Exception $e) {

Is this the desired behaviour when using a query, or is it related to this bug?

(Tested on 2.4.0 and 2.4.1)

Comment by Jiri Kavalik [ 22/Jan/14 ]

When this is revived, I noticed that $em->lock($entiy, PESSIMISTIC_WRITE); doesn't refresh too. If it is not supposed to, it might be noted in documentation or in http://docs.doctrine-project.org/en/2.0.x/reference/transactions-and-concurrency.html

Comment by Marco Pivetta [ 22/Jan/14 ]

Renaud Drousies Jiri Kavalik can you please open separate (detailed) issues for those problems?

Comment by Renaud Drousies [ 22/Jan/14 ]

Done! See DDC-2929

Comment by Jiri Kavalik [ 23/Jan/14 ]

Done in DDC-2930

Generated at Sat Apr 19 01:48:02 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.