> The test case is simple.
> ....
> On the second pass, the attempt to prepare the first query against the
> second connection will fail with this message:
>
> org.firebirdsql.jdbc.FBSQLException: GDS Exception. 335544343. invalid
> request BLR at offset 64
> table id 198 is not defined
> <snip ... call stack >
>
> Is this (a) a known constraint of FB (deliberate optimization), (b) a
> new bug that needs to be reported, (c) an old bug that is resolved in
> FB2, or (d) something that is a function of the jaybird JDBC connector
> (which I would then need to report to the firebird-java list)?

I would say that it smells like a bug, at least in case of normal execution
(e.g. optimization case) there should be different exception.

This can be JayBird bug too, since prepared statements are cached when you
use connection pooling and do not switch it off. In combination with Classic
it can produce some funny issues due to metadata cache implementation there.

May I ask to you prepare a test case that reproduces the issue in your
environment, I will try then to run it in mine. If it executes fine, we
should look for an error in your Fedora distribution (did you build it
yourself?). If it fails, we try it with Firebird 2.0, JayBird 2.0 beta and
so on.

The test case is needed to be able to check the issue reliably.

Roman