Steps for detecting a collaboration deadlock

By default, the InterChange Server Express system performs deadlock detection automatically when you start InterChange Server Express. However, when deadlock detection is performed, startup of InterChange Server Express can be delayed if a collaboration group contains many collaboration objects, because InterChange Server Express must traverse all the collaboration objects in the group to determine whether there is a deadlock in the group. This can cause slow startup even when no deadlock exists.

You can configure the InterChange Server Express system to not perform deadlock detection. If you do so, the system starts collaboration groups without first checking for deadlocks. This can make it possible for InterChange Server Express to boot more quickly. However, if deadlock detection is not performed and a deadlock exists, an event that is later sent to a collaboration may fail.

System Manager does not provide the ability to set the DEADLOCK_DETECTOR_CHECK configuration parameter. Instead, to set this configuration parameter, you must edit the InterchangeSystem.cfg file and change the parameter's value in this file.

Perform the following steps to configure the InterChange Server Express system for deadlock detection:

  1. Open the InterchangeSystem.cfg file. The following lines define the DEADLOCK_DETECTOR_CHECK parameter in the file:

    <tns:name>DEADLOCK_DETECTOR_CHECK</tns:name>

    <tns:value xml:space="preserve">false</tns:name>

  2. If you want deadlock detection performed, change the false value to true.
  3. If you do not want deadlock detection performed, change the value to false.

Copyright IBM Corp. 2004