On 2016-12-08 13:50, hugo.larson@... [Firebird-Java] wrote:

> Hi,
>
> I can tell you that the problem is much more obvious with jaybird 3.

By the looks of it, this specific error occurs because a
ResultSetMetaData method needs to query the database while there is no
active transaction. Normally a query to the database would start a new
transaction, but in the specific context of the ResultSetMetaData it
can't do that and it would normally 'piggyback' on the current
transaction.

I'll try to fix it, but that is unfortunately not guaranteed to prevent
the other problems you also experienced with Jaybird 2.2, although I
will check if there are other places where a similar problem can occur.

Mark