Subject | Re: [ib-support] Transactions |
---|---|
Author | Jason Chapman (JAC2) |
Post date | 2002-06-27T11:32:33Z |
""mivi71dk"" <Michael.Vilhelmsen@...> wrote in message
news:afcbck+57me@......
active, it will staty the same until that oldest active transaction is
committed or rolled back by the client holding the transaction. In the
above case it is likely to be the tool that you are using to look at the
transaction.
periodically and after persistant fails, it decides the client has gone away
and notes a 10054 (if using a tcp/ip connection).
This can be a bit misleading as the client EXE may have crashed, but
gds32.dll on the client may still be alive and responding to the ping.
Anyway, typically 2 minutes + before the serve issues a rollback.
rollback.
The oldest active often due to clients leaving their machines on.
cleared by a sweep.
Cheers,
JAC.
news:afcbck+57me@......
> HiThis is exactly what it says on the tin, i.e. the oldest tx that is still
> Oldest transaction 1574
> Oldest active 16689
> Oldest snapshot 16689
> Next transaction 16690
> 1.
> A Rollback.
> But When I disconnect from the DB correctly, the values changes to
> almost the same.
>
> QUESTION
> Will the Oldest Active stay as is, until I do a disconnect from the
> DB ?
active, it will staty the same until that oldest active transaction is
committed or rolled back by the client holding the transaction. In the
above case it is likely to be the tool that you are using to look at the
transaction.
> 2.When the server realises the client has gone away. It pings the client
> A crash on the client side.
> This will make some transactions "hanging".
>
> QUESTION
> When will they be released ?
periodically and after persistant fails, it decides the client has gone away
and notes a 10054 (if using a tcp/ip connection).
This can be a bit misleading as the client EXE may have crashed, but
gds32.dll on the client may still be alive and responding to the ping.
Anyway, typically 2 minutes + before the serve issues a rollback.
> Another appl. uses BDE to connect.Bear in mind that the BDE can start its own transactions as well.
> Here I use standard D5 DB Comp.
> Here I can only do a StartTransaction, a Commit or a Rollback.
> Whenever I do a StartTransAction, I always do a Commit or a Rollback
> as well.
> My clients all uses BDE version 5.11.The oldest transaction sticks when you change some data and then issue a
> When testing here in my own network, I never got my transactions fra
> from each other.
> But they do on my customers LAN.
rollback.
The oldest active often due to clients leaving their machines on.
> On some occations I have gotten my own values some away from eachThe oldest is the only one that should stick at this point. It will be
> other, but they have always come close togehter when the connection
> to the DB closes.
cleared by a sweep.
Cheers,
JAC.