Not very long, probably an hour. This is a test system so we had the
luxury of being able to restart in so we could continue with our work.

For the configuration file, this is the closest thing I could find, but
I don't think it applies:
# ----------------------------
# Client Connection Settings (Basic)
#
# Seconds to wait before concluding an attempt to connect has failed.
#
# Type: integer
#
#ConnectionTimeout = 180

I'm assuming the default timeout is three minutes, and we waited longer
than that.

-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Ann W. Harrison
Sent: Tuesday, April 19, 2005 11:15 AM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Rolling back old transactions


Rick Debay wrote:

> We had some long running transactions that we were unable to commit
> because the client was rebooted.
> Looking at the statistics, there is a gap and no one is attached.
>
> Gfix -l doesn't return anything. Sweep doesn't change anything. We
> ended up restarting the server. Is there any way to close the
> transaction gap besides bouncing the server?

In theory, the server checks with its clients at some interval -
probably controlled by the configuration file. If the client is gone,
the server should be shutting down the connection which will rollback
open transactions. How long did you wait before shutting down the
server?


Regards,


Ann




Yahoo! Groups Links