-----BEGIN PGP SIGNED MESSAGE-----
<firstname.lastname@example.org> wrote in message
> We have an app which opens a transaction, runs a couple of stored
> procedures and commits/rolls the changes. It so happens that for
> unknown reasons the application crashes while in the middle of a
> tran and of course the locks it has accumulated are not released.
> About 2 hours later the sybase errorlog says:
> "Process id xxx (the one holding the locks) killed by hostname
> yyyy, Host id zzzzz"
> In the meantime we have a lot of processes blocked for a very long
> The question is how we can make sybase resolve such situations in a
> more prompt manner. I seem to recall that there is something
> called "heartbeat" which in essence causes sybase to check if the
> client is still alive. Is there a parameter controlling how
> frequently this is done?
> Thank you for your suggestions.
> Lubo Vitkov
In your OS you have to configure the TCP_KEEPALIVE (or whatever it is
called in your OS)
"It came from outer space, born in the heart of a sun"
Senior Consultant Sybase Professional Services
pgp key available
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1
-----END PGP SIGNATURE-----