Yes, I have done that (breakpoint on setLockMode) and it is not called
before these log outputs:
2018-01-03 11:04:28 lock: 1 exclusive write lock requesting for SYS
2018-01-03 11:04:28 lock: 1 exclusive write lock added for SYS
2018-01-03 11:04:28 lock: 1 exclusive write lock unlock SYS
...
...
Answer this: Is LOCK_MODE=0 to disable ALL locking or just some locking?
The documentation suggests ALL locking is disabled.
And if the answer is ALL, then clearly from the log file this is not
happening.
For testing I added code:
this.lockMode = ci.getProperty("LOCK_MODE", Constants.DEFAULT_LOCK_MODE);
to constructor:
Database(ConnectionInfo ci, String cipher)
and the original log locking output was removed. However, I don't fully
understand the locking design to know if this correct.
This is why I shared my analysis to help focus developer's attention.
Patrick
On Wednesday, January 3, 2018 at 10:25:40 PM UTC-8, Noel Grandin wrote:
>
>
>
> On 4 January 2018 at 02:22, Patrick H <teng...@gmail.com <javascript:>>
> wrote:
>
>> Constructor, public Database(ConnectionInfo ci, String cipher) where all
>> the URL options are parsed never parses for the 'LOCK_MODE' option. Thus
>> never changes the default value for Database.lockMode which is
>> Constants.DEFAULT_LOCK_MODE (3).
>>
>>
> It's not obvious how this works - set a breakpoint in Database.setLockMode
> and you'll see how it parses the options from the URL.
>
--
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 h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
