Hi Dario, We're using H2 as storage back-end for JMS. JBoss uses HSSQL by default, but we had a lot of problems with it, so we searched many options to replace it and after some tests we decided to use H2. We're using it on a Red Hat EL 5 with ext3 as filesystem. I tested several parameters in the connection string, and for us nioMapped was slightly faster than nio and much faster than regular fs.
We're using it in production already, appart from little problems it's behaving quite well. But we're not using it as our main DB, only as JMS back-end. I hope this helps. Regards. On Aug 24, 8:25 pm, Dario Fassi <[email protected]> wrote: > Hi Borja, > Apart from the reported issue, you may tell us about your experience with the > use of nioMappedFs ? > I'm interested in base OS used, performance comparison with regular FS and > motivation to use it. > Are you using this in production or testing ? > > regards > Dario > > El 24/08/10 09:22, Borja escribió: > > > > > > > > > We're using H2 (version 1.2.140) with connection string > > "jdbc:h2:split:nioMapped:/ > > testDB;LOCK_MODE=3;CACHE_SIZE=262144;TRACE_LEVEL_FILE=0;DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE" > > and we have a NullPointerException with this stack: -- 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.
