Hello,
While running the H2 database in remote tcp mode over Windows (Windows 7 to
be exact), I have noticed that it becomes unresponsive when multiple
queries hit it in short period of time. I have enabled tracing and am
seeing logs such as:
/*SQL #:1*/CALL LOCK_MODE();
03-28 12:16:29 lock: 2 shared read lock requesting for MY_TABLE_NAME
03-28 12:16:29 jdbc[2]:
/*SQL l:50 #:1*/SELECT NAME FROM MY_TABLE_NAME WHERE ID = ? {1: 26};
03-28 12:16:29 jdbc[2]:
/*SQL #:1*/CALL LOCK_MODE();
03-28 12:16:29 lock: 2 shared read lock requesting for MY_TABLE_NAME
03-28 12:16:29 jdbc[2]:
/*SQL l:50 #:1*/SELECT NAME FROM MY_TABLE_NAME WHERE ID = ? {1: 27};
03-28 12:16:29 jdbc[2]:
/*SQL #:1*/CALL LOCK_MODE();
03-28 12:16:29 lock: 2 shared read lock requesting for MY_TABLE_NAME
03-28 12:16:29 jdbc[2]:
/*SQL l:50 #:1*/SELECT NAME FROM MY_TABLE_NAME WHERE ID = ? {1: 28};
03-28 12:16:48 jdbc[2]:
/*SQL */ROLLBACK;
03-28 12:16:48 database: disconnecting session #2
03-28 12:16:48 database: closing C:/H2/db/data/my_db_name
03-28 12:16:48 lock: 1 shared read lock requesting for LOBS
03-28 12:16:48 lock: 1 shared read lock requesting for LOBS
(followed by a few hundreds of logs related to shutting down the database)
I setup a Red Hat 5 virtual machine over that Windows 7 host, installed H2
database on the Red Hat machine and problem has disappeared. I have also
never seen this problem while working in embedded mode on Windows 7 (but
maybe this is just because it is running locally?).
Is this a known issue for Windows in server mode? Is there any workaround?
I have tried with both 1.3.171 and 1.3.165.
Thank you in advance,
Yanni.
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
