Subject | RE: [Firebird-Java] Local Transaction Active |
---|---|
Author | Robert DiFalco |
Post date | 2004-08-27T14:10:05Z |
Another suggestion on this if the bug cannot be found...
Might it be a good idea to also close the connection before throwing
this exception? The connection is bad anyway and this will make sure
that the user gets "connection closed" errors if they continue to use
it. This way generic connection pools will cycle out that connection.
Just a thought.
R.
-----Original Message-----
From: Roman Rokytskyy [mailto:rrokytskyy@...]
Sent: Wednesday, August 25, 2004 10:33 PM
To: Firebird-Java@yahoogroups.com
Subject: Re: [Firebird-Java] Local Transaction Active
able to fix it before the release.
Roman
Might it be a good idea to also close the connection before throwing
this exception? The connection is bad anyway and this will make sure
that the user gets "connection closed" errors if they continue to use
it. This way generic connection pools will cycle out that connection.
Just a thought.
R.
-----Original Message-----
From: Roman Rokytskyy [mailto:rrokytskyy@...]
Sent: Wednesday, August 25, 2004 10:33 PM
To: Firebird-Java@yahoogroups.com
Subject: Re: [Firebird-Java] Local Transaction Active
> Roman, I think I can make it happen reliably in a somewhat contrivedThanks! I will try to reproduce it on my laptop. Hopefully I will be
> way. All I need to do is stop the database while my application is
> still running. While this may be contrived, I think it might point to
> the problem. Because the exception I would expect is something like:
>
> org.firebirdsql.gds.GDSException: Unable to complete network request
> to host "localhost".
>
> And not "Local Transaction in Use".
able to fix it before the release.
Roman