These debug parameters might require a large amount of disk space, dependent upon when the server encounters problems the longer the server stays up, the larger the debug files will be. There may be issues surrounding their use, or special precautions that must be considered. "Session semaphore held for seconds."īefore enabling any debug parameters, discuss them with IBM Support beforehand. The second way of determining if there is a semaphore issue, is when you see (at the server console) the following message: Error: "Session semaphore held for seconds" New to Domino 4.5, AdminP's semaphore for ACL modificationĢ. Handle table free chain consistency semaphore The following table lists some of the semaphores you may encounter: Semaphore It is not unusual on a heavily used server to get semaphore timeouts. The second number is a decimal number which shows the number of times the semaphore timeout occurred. For example, 0x030B is the collection semaphore used by NIF. The ID tells us what the semaphore is used for. The statistic Sem.Timeouts will not appear in the Statrep if the customer is not experiencing semaphore timeouts. If the problem has occurred, you will see something similar to the following, depending upon the nature of the semaphore timeout To view this statistic, type the following: Sem.TimeoutsĪt the server console, you will see the Sem.Timeouts statistic. If an issue is a semaphore issue, it will be reported in two ways: 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |