At 08:30 PM 21/02/2006, you wrote:

>"The server will eventually discover the connection",
>but how long will it take the server to discover the
>dead connection?. Ok, i can use the NOWAIT transaction
>on the other application, but that doesn't solve my
>problem, if i can't update those records and wait a
>long time for the server to discover the dead
>connection. Is there any faster way to discover the
>dead connection and do a rollback of that transaction
>?

You have to wait for the server to discover the dead connection. The
time it takes depends on the Keep Alive setting (assuming Windoze) in
the server host's Registry.

Quoting from http://www.winguides.com/registry/display.php/891/

Control Keep Alive Parameters (Windows NT/2000/XP)
These settings control how Windows manages connection keep alive
transmissions. Including the timeout before keepalives are sent and
the interval between keepalive transmissions.

Open your registry and find the key below.

Create new DWORD value named "KeepAliveTime" and set it to equal the
number of milliseconds to wait before sending keep alive packets (the
default is 2 hours - 7,200,000 milliseconds).

Also create a new DWORD value called "KeepAliveInterval" and set it
to equal the time in milliseconds between retransmissions of
keepalives, once the KeepAliveTime has expired (the default is 1
second - 1000 milliseconds).

Restart Windows for the change to take effect.

For Linux, there's a good description of tweaking the equivalent
settings for the tcp/ip stack here:

http://publib.boulder.ibm.com/wasce/V1.0/Tasks/Tuning/Linux.html

./hb