I have witnessed something similar with the IBM jit. I think you can be fairly sure that the jit is the problem here as it works interpreted and on all other JVMs. The only other possibility being that the jit uncovers a race condition that is not triggered elsewhere, or is in some way system specific.
IIRC for us the problem actually went away when changing the byte code compiler from the eclipse one to the sun one. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
