How do you turn on semaphore debugging parameters in the notes.ini for Domino?
FOR DOMINO 5.0.9 - DOMINO 6.0.2:
DEBUG_CAPTURE_TIMEOUT=10 ---> Will add timestamps to the semaphore debugging if used instead of DEBUG_CAPTURE_TIMEOUT=1, which can be extremely useful.
The semaphore timeout messages will be written to SEMDEBUG.TXT, which in release 5.x gets created under the Notes program directory, or under the Notes Data directory on UNIX platforms. In release 6.x, this file is created in the IBM_TECHNICAL_SUPPORT directory on all platforms.
FOR DOMINO 6.0.3 OR HIGHER and DOMINO 7:
DEBUG_CAPTURE_TIMEOUT=1 ---> No longer any need to set this equal to 10 in order to get time stamps. Setting this equal to 10 will actually dump out the contents of the semaphore structure (which may be useful in some cases, but not in most).
Note: For Domino 6.5.1, 6.5.2 and 6.5.3 servers you must use DEBUG_CAPTURE_TIMEOUT=1. Domino 6.5.1, 6.5.2 or 6.5.3 will get to deadlock if the server is configured with DEBUG_CAPTURE_TIMEOUT=10. (see technote #1191121).
The semaphore timeout messages will be written to SEMDEBUG.TXT, which gets created under the IBM_TECHNICAL_SUPPORT directory
X (default 30000, which is in milliseconds, so 30000 will translate into 30 seconds since there are 1000 milliseconds in 1 second). Use as instructed by your support provider to change how long a semaphore must timeout before getting reported.
Debug_ThreadID=1 This prefixes the console output with the process and threadid information in the format [ProcessID:Virtual Thread ID-Native Thread ID]. This can be helpful in identifying the process or thread holding a semaphore.