Browse Prior Art Database

Domino Addin Task to Monitor Semaphore Timeout Conditions

IP.com Disclosure Number: IPCOM000198663D
Publication Date: 2010-Aug-11
Document File: 1 page(s) / 19K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for systematic monitoring the SEMDEBUG.txt file, parsing its content, and automatically launching NSD.exe when a specified threshold of reported timeouts has been met in the given polling interval. This reduces the need for constant observation by a systems administrator and the manual launching of NSD.exe, increasing the likelihood that semaphore timeouts are addressed in an efficient manner.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 80% of the total text.

Page 1 of 1

Domino Addin Task to Monitor Semaphore Timeout Conditions

The Domino server uses semaphore mechanisms to protect database resources for multi-threaded access. When multi-threaded processes attempt to lock semaphore structures, they might have to wait for another process or thread to free the semaphore. When these wait times are excessive, the server reports semaphore timeouts in a text file called SEMDEBUG.txt. These timeout reports are a vital troubleshooting tool, but it is often necessary to correlate the data in SEMDEBUG.txt to the data collected by the NSD.exe utility, which extracts call stacks and memory data from the Domino server during runtime execution.

Currently, system administrators are required to monitor the server and manually launch NSD.exe. Unfortunately, semaphore timeouts often occur when no server administrator is available to do this, and the condition that precipitated the timeouts might have passed by the time the NSD data is collected.

This invention monitors the SEMDEBUG.txt file, parses its content, and automatically launches NSD.exe when a specified threshold of reported timeouts has been met in the given polling interval.

This invention runs as an addin task to the Domino server. Internally, it opens SEMDEBUG.txt, parses the timeout data stored there, and compares those data to the thresholds set via configuration parameters on the Domino server. If a specified number of timeouts has been reported since the last time the file was exa...