There is probably something wrong with the current state of your
connection, but the driver is losing track of the original exception
because another exception occurred when cleaning up after the first
exception.

Do you have the source code? The easiest to get the exception would be
to add a ge.printStackTrace(System.out) to the checkFatal function
indicated below. The original exception will probably explain what is
going on.


-----Original Message-----
From: Robert (Jamie) Munro [mailto:rjmunro@...]
Sent: Friday, May 30, 2003 12:04 PM
To: Firebird-Java@yahoogroups.com
Subject: [Firebird-Java] Can't destroy managed connection with active
transaction

What does this mean?

java.lang.IllegalStateException: Can't destroy managed connection with
active transaction
at
org.firebirdsql.jca.FBManagedConnection.destroy(FBManagedConnection.java
:333
)
at
org.firebirdsql.jca.FBStandAloneConnectionManager.connectionErrorOccurre
d(FB
StandAloneConnectionManager.java:84)
at
org.firebirdsql.jca.FBManagedConnection$2.notify(FBManagedConnection.jav
a:11
21)
at
org.firebirdsql.jca.FBManagedConnection.notify(FBManagedConnection.java:
1094
)
at
org.firebirdsql.jca.FBManagedConnection.checkFatal(FBManagedConnection.j
ava:
726)
at
org.firebirdsql.jca.FBManagedConnection.executeStatement(FBManagedConnec
tion
.java:791)
at
org.firebirdsql.jdbc.FBConnection.executeStatement(FBConnection.java:107
2)
at
org.firebirdsql.jdbc.FBStatement.internalExecute(FBStatement.java:908)
at
org.firebirdsql.jdbc.FBStatement.executeUpdate(FBStatement.java:146)
at org.viva.fibre.Exporter.exportPacket(Exporter.java:167)


All I did was this:
Statement stateTemp = dbConn.createStatement();
sql = "UPDATE \"FiBRE$Inserts\" SET \"FirstExport\" = " +
exportID.toString() + " where \"FirstExport\" = 0;";
rowCount = stateTemp.executeUpdate(sql);

Robert Munro




To unsubscribe from this group, send an email to:
Firebird-Java-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/