On 8/23/2011 6:38 AM, Bergquist, Brett wrote:
Sorry Kathey I spelt your name wrong in the previous response :(
No worries. BTW if you want an XA issue to sink your teeth into and
provide context , you might want to look at DERBY-1016.
https://issues.apache.org/jira/browse/DERBY-1016
I think
Re: Have a database that has a phantom "transaction" even after
booting the database clean in embedded mode
On 8/23/2011 5:21 AM, Bergquist, Brett wrote:
> I guess I was under the assumption that it would go away if I booted the
> database clean. It seems to me that a database that has
Thanks Kathy. I will do some reading on this.
-Original Message-
From: Kathey Marsden [mailto:kmarsdende...@sbcglobal.net]
Sent: Tuesday, August 23, 2011 9:19 AM
To: derby-dev@db.apache.org
Cc: Bergquist, Brett
Subject: Re: Have a database that has a phantom "transaction"
On 8/23/2011 5:21 AM, Bergquist, Brett wrote:
I guess I was under the assumption that it would go away if I booted the
database clean. It seems to me that a database that has been stopped and
booted clean would invalidate an existing transactions and clean them up. Is
this not the case with
help me understand this!
Brett
-Original Message-
From: Knut Anders Hatlen [mailto:knut.hat...@oracle.com]
Sent: Tuesday, August 23, 2011 4:16 AM
To: derby-dev@db.apache.org
Subject: Re: Have a database that has a phantom "transaction" even after
booting the database clean i
"Bergquist, Brett" writes:
> I have a database that shows a phantom "transaction" even after
> booting the database in embedded mode. This is Derby 10.8.1.2. The
> database has >600 log files in the "log" directory. I connect to the
> database using IJ in embedded mode and it takes a while for th
