In the meantime I probably found the reason but for this I need to explain a bit more. The test case is running on multiple threads, each thread has his own connection to the database. Each thread listens to a MQ queue for getting messages. For each message two merge statements are performed, the second merge is always on the same record.
When not using auto commit I see H2 method org.h2.command.Command.filterConcurrentUpdate using a lot of cpu time in performance monitoring. When using auto commit filterConcurrentUpdate isn't called at all. -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
