> After a network change, the connection is
> not possible until I restart xinetd (I run firebird from xinetd)
> but even then, the code fails as described.
> I am not sure why, as all other databases and services are quite
> happy with the network changes,

You mean the same instance of Firebird or other database servers? If
latter, then try to report this either to Firebird-Support or to
firebird-devel list, it might be a bug in Firebird too.

> And why would it only fail on that method ?!
> All the other calls (updates, inserts etc) are all fine!

That method does not look very nice. JayBird has a concept of
auto-transaction, that's a transaction that is automatically started
when no current transaction is available (mainly needed for
auto-commit mode). It is handled through a corresponding flag in
AbstractConnection class and it is very sensitive. I will try to come
with a more stable scheme.

> Mostly solved.

What do you mean?

Thanks!
Roman