Infinity ASP.NET WebHealth Events
-
Before creating the application lock, the code raises an ASP.NET WebHealth event named InfoBusinessProcessDetailMessage stating "Business process: CreateAppLock entered."
-
After the lock is acquired, an ASP.NET WebHealth event is raised named InfoBusinessProcessDetailAppLockAcquired stating "Business process status application lock acquired."
-
The code then attempts to get an application lock for the specific parameter set using "BPappLock:" & ParameterSetID as the lock name. Before the lock is attempted, a "Business process: CreateParameterSetAppLock entered" WebHealth InfoBusinessProcessDetailMessage is raised. Web events are raised if a lock cannot be achieved. If the business process is already running, a message of "Business process parameter set application lock not acquired, return code=X" along with error information including "The business process '<Your BP Spec Name>' is already running.
Lock Status Code | Description |
---|---|
0 |
Lock was successfully granted synchronously. |
1 |
Lock was granted successfully after waiting for other incompatible locks to be released. |
-1 |
Lock request timed out |
-2 |
Lock request was canceled |
-3 |
Lock request was chosen as a deadlock victim. |
-999 |
Parameter validation or other call error. |
Note: The Infinity platform and the applications that are built on it have been instrumented using the standard ASP.NET WebHealth system. This system allows the application developer (Blackbaud) to efficiently surface diagnostic, security, auditing, and logging information about the inner workings of the application. An administrator then uses a built in configuration system to tap into this stream of information and route the particular events of interest to various consumers of the information. For more information, see Monitor Infinity Web Server Events with PowerShell and WMI.