Hi Michel, I've never seen such issue regarding to H2. Normally this is caused by a bug from other parts of the software. Nevertheless I think you should run a profiler on your application in order to be more accurate finding out which thread is getting 100% of your CPU. Java does provide a very good tool for this job called jvisualvm: http://docs.oracle.com/javase/6/docs/technotes/tools/share/jvisualvm.html
There's other paid options like jprofiler, yourkit, etc. But jvisualvm will probably show you what's is going on. Cheers -- Márcio Geovani Jasinski -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
