We're using H2 to embed a database with our product for some months now and
we really appreciate the functionalities of H2.
We're using the auto-mixed (AUTO_SERVER) mode in order to allow concurrent
access from several processes without imposing our customers to set up a H2
server. This works fine but one of our customer recently complained that
its connection to the database was too slow. So we asked him to activate
the traces in order to get more information and we realized that putting
the file lock on the database indeed took 2 minutes. Such a delay is not
acceptable for our customer.
Here is an extract of the log our customer gave us :
[...]
17:26:34.475 INFO h2database - big:database opening
C:/PSOCGEN/WBIG/BIGBASES/big (build 168)
17:26:34.475 DEBUG h2database - big:fileLock load {method=file,
id=13ae5fbf3f5e871d65716139fb167107b5b605250b8}
17:26:34.522 DEBUG h2database - big:fileLock load {method=file,
id=13ae5fbf3f5e871d65716139fb167107b5b605250b8}
17:26:34.522 DEBUG h2database - big:fileLock save
{id=13ae5fe889a9f541ad0ae7697cce954ae1c3f81b439, method=file}
17:26:36.522 DEBUG h2database - big:fileLock load {method=file,
id=13ae5fe889a9f541ad0ae7697cce954ae1c3f81b439}
17:26:36.522 DEBUG h2database - big:fileLock save
{id=13ae5fe889a9f541ad0ae7697cce954ae1c3f81b439, method=file}
*17:26:36.554 DEBUG h2database - big:fileLock load {method=file,
id=13ae5fe889a9f541ad0ae7697cce954ae1c3f81b439}*
*17:28:36.710 DEBUG h2database - big:fileLock save
{server=192.32.86.230:8090, id=13ae5fe889a9f541ad0ae7697cce954ae1c3f81b439,
method=file}*
17:28:36.725 DEBUG h2database - big:pageStore log recover
17:28:36.725 DEBUG h2database - big:pageStore log recover stage: 0
17:28:36.725 DEBUG h2database - big:pageStore log recovery completed
17:28:36.725 DEBUG h2database - big:pageStore log recover stage: 1
17:28:36.725 DEBUG h2database - big:index PAGE_INDEX_DATA opened rows: 149
17:28:36.725 DEBUG h2database - big:pageStore addMeta id=0 type=0 root=12
parent=0 columns=0,1,2,3
17:28:36.725 DEBUG h2database - big:index T0_DATA opened rows: 354
17:28:36.725 DEBUG h2database - big:pageStore addMeta id=2 type=0 root=11
parent=2 columns=0,1,2
17:28:36.725 DEBUG h2database - big:index T2_DATA opened rows: 0
17:28:36.725 DEBUG h2database - big:pageStore addMeta id=6 type=0 root=9
parent=6 columns=0,1,2,3,4
[...]
Such a lock is almost immediate in our own configurations. What can explain
this 2 minutes delay ? We thought our customer might have a firewall
slowing the available port search and we asked him to force the value of
the port using AUTO_SERVER_PORT but that changed nothing. On the other
hand, not using the AUTO_SERVER mode made the connection very fast (but
this could be done only for test and cannot be kept in production).
Any help of any kind would be much appreciated since we don't know what to
investigate.
Thanks by advance
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/h2-database/-/Q-n6XCrCaZEJ.
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.
