Hi, I am getting exceptions stating "Missing lob entry" on concurrent update and read of a row in the table. i.e. one thread/connection is reading(in loop) meanwhile another thread comes and updates the CLOB. After that when the previous thread reads the row, it is failing with high probability.
My connection URL is as follows: jdbc:h2:/data/database/;MVCC=true;CACHE_SIZE=2621440;PAGE_SIZE=4096;ALLOW_LITERALS=NUMBERS;LOCK_TIMEOUT=10000" The only way I am able to get rid of this issue is by setting transaction isolation level to serialize e.g. LOCK_MODE=1;MVCC=false; We are worried that removing the MVCC flag could reduce the performance a lot. The application should be able to serve million requests at any give time. Are we correct here ? We were on 1.3.176 earlier but updating to 1.4.192 has not helped either. Solutions that have not worked for us yet.. mv_flag=false SELECT ... FOR UPDATE Are we missing something here? Please let us know what extra data we can provide to help you guys. Thanks -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
