how we can get JPA EntityManager Flush work

18,956

You're flushing, but you're not committing - or otherwise ending the transaction / session which is likely configured for auto-commit.

Yes, after calling flush(), the DBMS is now aware of your data - but following ACID standards, no other database sessions will see this data until the DBMS is told to commit it.

Without knowing additional details about the architecture behind the rest of your application, etc., you're probably looking to do something like:

em.getTransaction().commit();
Share:
18,956

Related videos on Youtube

Nav
Author by

Nav

Updated on June 07, 2022

Comments

  • Nav
    Nav almost 2 years

    my question is why flush doesn't work :

    public void ejbService(){
       Customer c = em.find(Customer.class,1);
       c.setName("newName");
       em.flush();
       //at this point when I query mysql table I can not see "newName"
    
    
       thread.sleep(10000);
    
       c.setName("anotherName");
    }
    

    After finishing the method I see "anotherName" in the db also I check it with em.find(Customer.class,1,Lock.None); but still not work

    RGDS

  • Nav
    Nav over 12 years
    I also change flush mode to commit instead of auto but nothing happens
  • ziesemer
    ziesemer over 12 years
    Most JPA implementations will cache operations within the JVM (within the EntityManager). flush() merely forces these operations to be sent to the database, etc. - but does not imply a commit. stackoverflow.com/questions/4275111/… has some additional details / discussion that may be helpful to you.
  • ziesemer
    ziesemer over 12 years
    Setting the flush mode to commit is thinking about this backwards. This tells the EntityManager to only flush on commit. It doesn't mean to commit on flush.
  • SteveT
    SteveT over 11 years
    This is a subtle detail, but flush mode of commit does not mean flush ONLY on commit. It means ALWAYS flush on commit; but flush could also happen at other times, depending on the JPA provider.