IBM Support

About deadman lock time-outs

Question & Answer


Question

What are IBM® Rational® ClearCase® deadman lock time-outs?

Answer

A deadman lock time-out occurs when a Rational ClearCase server process detects a client process is holding a lock and is not responding within a set limit of time.

To prevent deadlock situations whereby other client processes remain in a wait state for the lock to be released by the non-responsive client, the server process will terminate the connection of the non-responsive client and release the locks.

Typical examples of deadman lock time-out scenarios include, but are not limited to:

  • Client loses its network connection.

  • VOB elements owned by users or groups not present in current domain. Check with vob_siddump.

  • Client process hangs or loops endlessly.

  • Client process takes too long to complete an operation.

  • Client host machine crashed or rebooted.

The time-out values for the deadman time-out value is set to 90 seconds.



For general information on Improving VOB Host Performance, refer to IBM Rational ClearCase Administration Guide.

Documentation

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Database","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF015","label":"IRIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0;7.0.1;7.1;7.1.1;7.1.2;8.0;8.0.1;9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Database","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21119236