On Mon, 08 Nov 2010 13:53:00 Helen Borrie wrote:

>
> I see you are dual posting this thread in two lists. May I remind you that
> firebird-devel isn't for support questions?

Apologies for the dual posting. There wasn't a response here for a couple of
days so I thought I might not get a reply here.

> I suspect the reason you're not getting "useful" answers about this is that
> you (and others who echoed your problem) forget that transactions and
> connections are instigated by the client, not the server. The server has
> no way to tell what is going on at a client. If the server doesn't get a
> commit or rollback request from a client for a transaction, or a detach
> request for a connection, then they simply stay alive until the operating
> system decides the connection is dead.
>
> Your OS will kick in eventually (4 hrs is the default on Windows for
> considering a non-responding network connection "dead") and inform the
> server that the connection is gone. After that, the server will tidy
> everything up, rolling back any open transactions and invalidating the
> attachment handle. Once they are gone, MON$ queries won't report them any
> more.

I understand this now, and clearly I need to focus on how the client is
handling exceptions. This wasn't obvious to me before and I suspect the others
with similar problems will also benefit from this explanation.

Regards

Tom