> I think you're right. No transaction is used in the testcase, when I
> explicitly use a transaction the exception disappears.

Then this is the reason.

> Is it possible to configure Jaybird like it will have the old, not
> according to the JDBC spec, behaviour? In read-only situations I don't
> always use transactions (is that bad?).

I can add this, but the issue most likely is somewhere else... I will check
your test case to see where Hibernate executes next query.

Roman