> Recently we tested JayBird 2.0 Beta 2. In our database update
> code we turn the auto commit mode on for DDL statements and
> off for DML. It runs without problems but while closing the
> connection the following exception is thrown:

Thanks! The reason most likely is that JayBird started a separate
transaction for metadata reads and did not commit it before the closing. I
will check if that's the case and will think for the workaround for it.

Roman