Subject | Re: [Firebird-Java] Re: Unrecognized transaction problem |
---|---|
Author | Roman Rokytskyy |
Post date | 2004-10-24T12:42:49Z |
Hi,
isc_badblk) for your query (it contains "WHERE blob_col = ?" and it seems
that server does not like such queries). In JayBird this error belongs to
the list of "fatal errors" and a transaction that caused it is destroyed.
After that goes "} finally {" block that tries to end a transaction, but
since it is already destroyed you get "unrecognized transaction" error.
I will check now if I can change the behavior of the driver to show
"internal error" instead of "unrecognized transaction" without big changes
in the code.
For now I do not consider this issue to be a showstopper for JayBird 1.5.4.
Roman
> Ah, if you leave out the try finally and the connection.close(), theI was able to find the reason. Server replies "internal error" (error
> Unrecognized transaction Exception is thrown at the executeQuery!
isc_badblk) for your query (it contains "WHERE blob_col = ?" and it seems
that server does not like such queries). In JayBird this error belongs to
the list of "fatal errors" and a transaction that caused it is destroyed.
After that goes "} finally {" block that tries to end a transaction, but
since it is already destroyed you get "unrecognized transaction" error.
I will check now if I can change the behavior of the driver to show
"internal error" instead of "unrecognized transaction" without big changes
in the code.
For now I do not consider this issue to be a showstopper for JayBird 1.5.4.
Roman