Semaphore lock acquisition problem (2 replies)
John, Semaphores are used internally to control the maximum number of concurrent instances of an IMan integration.
When we implemented this feature we tested very heavily to ensure that Semaphores would be released under all circumstances. We have had a reported issue whereby this wasn't the case, but we've not been able to replicate the issue.
Presently there is no means to clear the semaphores except for restarting the server/instance on which IMan is installed.
If you're still having issues after a restart, you clearly have been able to replicate the issue.
Thanks
Closed due to inactivity.
One of our jobs is giving us this message when it starts:
Job with ID [] failed to acquire semaphore lock or maximum concurrent job count reached.
This happens when we run the job scheduled for "Now". No other instances of the job are running. I don't see that message in emails sent when the job runs normally.
The problem started yesterday. We stopped and started IMan, stopped and started IIS, stopped and started SQL Server, and finally rebooted the server. The message persisted despite these steps.
Please help us to understand why IMan would detect a semaphore lock in this situation.
Is there a way to clear a semaphore lock? Is there danger in doing so if we are confident it is erroneous?
Thanks in advance.