--- In firebird-support@yahoogroups.com, "m_i_k_e_msg"
<m_i_k_e_msg@...> wrote:

>
> I've discovered a Firebird's major problem, and i don't know how to
> solve it.
> I have 2 apps updating the same record using transactions. If one app
> has a connection failure and didn't get the chance to commit, the
> other app hangs, waiting for the other app to commit, but that will
> never gonna happen, until you do a restart of the firebird server.
> If anybody knows a method on how to solve this problem, without the
> "dummy packet" option because that is not a safe one, i appreciate.
> Thanks.

The server will eventually discover the connection is gone and
rollback the transaction. The second app will then succeed. Of course
if you would be less optimistic, then simply change your second app to
use a NOWAIT transaction and if you try and change the same record
that would have hung your application, you will receive an exception
immediately. This behaviour is often (but not always) more useful.

Adam