On 04/06/2012 19:57, Katherine Marsden wrote:
On 6/4/2012 9:29 AM, John English wrote:
I'm on 10.8, and I only have about a dozen matching rows at the
moment. No stack trace that goes further than my own code; all I have
is stuff like this:
Check the derby.log for the error and full stack
Hello, all:
While trying to debug an anomaly within my app, I wanted to see all the active
transactions within Derby (in-memory mode).
However, accessing SYSCS_DIAG.TRANSACTION_TABLE table didn't prove very
useful, as it is not possible to identify what statements those transactions
execute,
Looks like a bug to me. The error XSCH4 Conglomerate could not be
created isn't being tested for in the Derby tests as far as I can
see. I also searched the bug tracker
(https://issues.apache.org/jira/browse/DERBY) in vain for this
particular error.
Looking in the code where the error is
Hi Pavel,
Note that the SQL_TEXT column will be null for any transaction which is
not currently executing a statement. If you turn on statement logging
(-Dderby.language.logStatementText=true), then your statement text will
be logged to derby.log. You can use the syscs_diag.error_log_reader()
Excellent! Thank you, Rick for your prompt response.
-Original Message-
From: Rick Hillegas [mailto:rick.hille...@oracle.com]
Sent: Tuesday, June 05, 2012 12:30 PM
To: derby-user@db.apache.org
Subject: Re: SYSCS_DIAG.TRANSACTION_TABLE
Hi Pavel,
Note that the SQL_TEXT column will be null
