Subject Re: [IBO] pessimistick locking - how to remove lock after client crash
Author G. Nau
okay, thanks for clarifying this issue.


Am 12 Mar 2007 um 21:16 hat Helen Borrie geschrieben:

> At 08:40 PM 12/03/2007, you wrote:
> >During row edit I activate "pessimistic locking" and "sync before
> >edit", which
> >is doing well.
> >Now some customers are reporting that after a client crash (power surge,
> >blue screens) the locking is still active and they are not able to edit that
> >locked row.
> >Sometimes the lock is going away after some timeout but sometimes it still
> >exists after 20 minutes leaving the crashed client switched off.
> >I then use /etc/init.d/firebird restart to completely restart
> >firebird 2.0 server to
> >get of that lock.
> >
> >My questions:
> >1. Is there a way to determine, which user or workstation has initiated a
> >lock?
> No, because, as far as the server knows, it is just an uncommitted
> transaction that has pending work. The TCP/IP timeout will kick in
> after the configured keepalive period (default is 2 hours on Windows
> and Linux) and then the server will flag the uncommitted record
> versions to be deleted.
> >2. is there a way to manually release a lock in such a situation?
> No. If this is a frequent problem, you might look at reducing the
> TCP/IP timeout terms of productivity, it would be cheaper
> to fix (or ban) the programs that are blue-screening and to do
> something about clean power for the operators!
> Helen
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> - your IBO community resource for Tech Info papers,
> keyword-searchable FAQ, community code contributions and more !
> Yahoo! Groups Links

Der fr�he Vogel f�ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: