Thanks for your replay. Yes it is a very large transaction. I solve it for now by increase the cache size. But this is only at temporary solution, because depend on the size I might ran into this problem again.
I think it will be fairly easy to set-up a test case that reproduce the error. I will get back when it's ready. Do you have any idea why I didn't see this in 1.1.110? br, Flemming Harms On Dec 3, 9:11 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > This is a warning message only, but it's strange that it shows up. Do > you use a very large transaction? Could you create a simple > reproducible test case? If not, no problem, there are other ways to > find out what's going on, but that would be the easiest way to > analyze. > > By the way CACHE_TYPE=TQ doesn't have an effect since version 1.1.119. > I found some problems with this cache algorithm, and according to my > test it's slower in most cases. That's why I have disabled it. In any > case it will use the CacheLRU implementation - see also the changelog. > > Regards, > Thomas > > On Wed, Dec 2, 2009 at 6:24 PM, fharms <[email protected]> wrote: > > Hi, > > > We are starting to see this error "database: Cannot remove records, > > cache size too small?" after we upgrade from 1.1.110 -> 1.1.119 and > > inserting a large number of records into one table (240.000). > > > /**/prep17249.executeUpdate(); > > 12-02 18:07:14 lock: 2 exclusive write lock requesting for > > CUSTOM_PROPERTY > > 12-02 18:07:14 database: Cannot remove records, cache size too small? > > 12-02 18:07:14 jdbc[2]: > > /*SQL l:69 #:1 t:8*/insert into custom_property (value, ownerUuid, > > name) values (?, ?, ?) {1: '', 2: '69f32aca- > > af8d-4294-9a87-2d98e09cfe2f', 3: 'Serial No'}; > > 12-02 18:07:14 jdbc[2]: > > /**/prep17249.close(); > > > our connection url look like this. > > > jdbc:h2:/database/ > > 127.0.0.1;CACHE_SIZE=32720;DB_CLOSE_DELAY=0;TRACE_LEVEL_FILE=0;TRACE_LEVEL_SYSTEM_OUT=0;CACHE_TYPE=TQ" > > > I could try to increase the cache_size, but I would like to understand > > the error message and why we are starting to see in 1.1.119 > > > Thanks in advance > > > br > > Flemming > > > -- > > > 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 > > athttp://groups.google.com/group/h2-database?hl=en. -- 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.
