The JVM that derby was running in crashed with a SEGV. There application
server also went down. When I brought both up, the database shows two XA
transactions in the PREPARE state (looking at syscs_diag.transaction_table) but
the application server has no reference to these transactions to
Bergquist, Brett bbergqu...@canoga.com writes:
The JVM that derby was running in crashed with a SEGV. There
application server also went down. When I brought both up, the
database shows two XA transactions in the PREPARE state (looking at
syscs_diag.transaction_table) but the application
longer to come up
with this myself.
Brett
-Original Message-
From: Knut Anders Hatlen [mailto:knut.hat...@oracle.com]
Sent: Tuesday, December 06, 2011 9:27 AM
To: derby-dev@db.apache.org
Subject: Re: how can I force a rollback of an XA transaction
Bergquist, Brett bbergqu...@canoga.com
.
The utility is basically what you suggested Knut.
Any ideas on where to go from here?
-Original Message-
From: Bergquist, Brett [mailto:bbergqu...@canoga.com]
Sent: Tuesday, December 06, 2011 9:50 AM
To: derby-dev@db.apache.org
Subject: RE: how can I force a rollback of an XA transaction
I
: Tuesday, December 06, 2011 11:45 AM
To: derby-dev@db.apache.org
Subject: RE: how can I force a rollback of an XA transaction
The database has the following transactions being show from querying
syscs_diag.transaction_table:
NPCAcv# sh /opt/csem/canogaview/app/scripts/solaris/gettrans.sh
ij
