Nevermind I see how the SET statement puts it in that settings map now. I was seeing the primordial sessions that were created before the connection url settings were being parsed. Unfortunately this doesn't explain why I saw a lock timeout despite the fact that I have the DEFAULT LOCK TIMEOUT set to 999999999... I'll keep digging... maybe overflow?
Is there a difference between putting LOCK_TIMEOUT and DEFAULT_LOCK_TIMEOUT on the url? On Tuesday, June 17, 2014 1:50:44 PM UTC-5, Steve Ash wrote: > > I am using H2 1.3.170 and am getting lock timeout errors while waiting for > shared locks. It is coming out of RegularTable.tryLock(). I have set > DEFAULT_LOCK_TIMEOUT and LOCK_TIMEOUT (not sure what is the difference in > the two) on the connection url and (at least for default lock timeout can > see it in INFORMATION_SCHEMA.settings as updated). In the constructor for > Session I see the lines: > > Setting setting = > database.findSetting(SetTypes.getTypeName(SetTypes.DEFAULT_LOCK_TIMEOUT)); > this.lockTimeout = setting == null ? Constants.INITIAL_LOCK_TIMEOUT : > setting.getIntValue(); > > This database.findSetting is never getting my lock settings back and thus > it is always defaulting to INITIAL_LOCK_TIMEOUT of 2000 ms. When I look in > database.findSettings -- I dont see anywhere that actually populates this > settings map. > > What am I missing here? > -- 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.
