Dear Noel,
I ran the trace option... relevant section pasted below.
Note: I left my desk at 11.50am... returned at 2:36pm... You can see also
"connecting session #50".
Not sure if this trace fragment will shed light into the issue or not.
However any guidance/ comments or thoughts much appreciated in advance.
05-27 11:50:22 jdbc[49]:
/*SQL l:316 #:1*/SELECT TABLE_CATALOG TABLE_CAT, TABLE_SCHEMA TABLE_SCHEM,
TABLE_NAME, COLUMN_NAME, ORDINAL_POSITION KEY_SEQ, IFNULL(CONSTRAINT_NAME,
INDEX_NAME) PK_NAME FROM INFORMATION_SCHEMA.INDEXES WHERE TABLE_CATALOG
LIKE ? ESCAPE ? AND TABLE_SCHEMA LIKE ? ESCAPE ? AND TABLE_NAME = ? AND
PRIMARY_KEY = TRUE ORDER BY COLUMN_NAME {1: '%', 2: '\\', 3: 'PUBLIC', 4:
'\\', 5: 'NOTES'};
05-27 14:36:31 database: connecting session #50 to Z:/Facilities/F&C
only/Cost Control/Databases/sunhao_net
05-27 14:36:31 jdbc[50]:
/*SQL */SET AUTO_RECONNECT TRUE;
05-27 14:36:31 jdbc[50]:
/*SQL */SET TRACE_LEVEL_SYSTEM_OUT 3;
05-27 14:36:31 jdbc[50]:
/*SQL */SET TRACE_LEVEL_FILE 3;
05-27 14:36:31 lock: 50 shared read lock requesting for MAIN
05-27 14:36:31 jdbc[50]:
/*SQL l:159 #:1 t:2*/SELECT * FROM \"SUNHAO_NET\".\"PUBLIC\".\"MAIN\" WHERE
( 1 = ? AND \"SUNHAO_NET\".\"PUBLIC\".\"MAIN\".\"PRID\" = ? OR 1 = ? AND
\"SUNHAO_NET\".\"PUBLIC\".\"MAIN\".\"PRID\" IS NULL ) {1: 1, 2: 1660, 3: 0};
05-27 14:36:31 lock: 50 shared read lock requesting for MAIN
On Sunday, May 26, 2013 7:16:46 PM UTC+4, Noel Grandin wrote:
>
> Try turning on the trace, and see what messages get written out when
> the disconnect occurs.
> http://h2database.com/html/features.html#trace_options
>
--
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.
