It would be interesting to see the client-side logs to see if there
anything useful about why the client disconnects.
Otherwise, you could try doing a Wireshark or Microsoft-Network-Monitor
trace of the connection, to see where and when the disconnect is initiated.
On 2013-05-08 11:08, Yanni Papadimitriou wrote:
Hello Noel,
Thank you for following up on this.
I thought of this possibility, but do you have any idea why this would
happen only if the server resides on a Windows machine and doesn't
happen when on a Linux machine? Client code is exactly the same no
matter what OS hosts the h2 server database.
Thank you,
Yanni.
On Wednesday, May 8, 2013 10:21:12 AM UTC+3, Noel Grandin wrote:
That sounds like your client is timing out for some reason and
disconnecting from the database.
On 2013-05-07 18:07, Yanni Papadimitriou wrote:
> 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] <javascript:>.
> To post to this group, send email to [email protected]
<javascript:>.
> Visit this group at
http://groups.google.com/group/h2-database?hl=en
<http://groups.google.com/group/h2-database?hl=en>.
> For more options, visit https://groups.google.com/groups/opt_out
<https://groups.google.com/groups/opt_out>.
>
>
--
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.
--
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.
