System Event Types
Only iCore runtime can create system-defined Events. Runtime can create system-defined Events of the following types.
The purpose of System Events is to:
- Connect system service part Jobs and make system service available in standard tracking.
- Define processing steps triggered by System events, such as starting execution of a Component when the system is started or execute some kind of error reporting Component when a Job fails.
Due to the nature of some of the System Event types they cannot be executed in a standard manner. Instead, some of them are executed locally by the System Event Processor (SEP) in the server instance that created them.
note
For System Event Jobs executing in the SEP context, it is not possible to invoke any of the Event creation functions and activities. If any Event is created from within such a Job an error log will be created. Execution of other Component configurations from within these Jobs are allowed but not recommended.
Note that most System Events have a special argument list (for example, __iCore_JobFailed Event type has arguments "ErrorMessage" and "JobId"). To create a Component configuration on a System Event, its Component definition must have a matching argument list. If not, the execution of the resulting Job will fail. Workflow is currently the only Component definition type that support custom arguments.
note
"Runs locally" specifies whether the Event type can be used in an Event configuration:
- "-" means the Event type is for internal use only.
- "Yes" means that Events of this type are processed in the Server instance that created the Event.
- "No" means that Events of this type are processed as regular "non-system" Events.
caution
Some system defined Event types that start a Job with a special argument list MUST be configured to start a Workflow with the correct argument list, otherwise execution will fail.
__iCore_ApplicationPoolDepleted
Created when a Job cannot be executed because an Application pool is full of only session Jobs. The Job that cannot be executed will remain in state 'dispatch pending'.
note
Solving this problem may require that you increase the number of available slots. For more information, see Server.
| Category: | Warning |
| Runs locally: | Yes |
| Created by: | Job manager |
| Available for Event Configuration: | Yes |
Arguments
| Name | Type | Description |
|---|---|---|
| ApplicationPoolId | Guid | ID of the depleted Application pool. |
__iCore_ApplicationPoolInstanceNotAvailable
Created when a Job cannot be executed because the configured Application pools are not implemented on a Server. The Job will keep its place in the process queue.
note
This problem can occur when, for example, a fail-over is initiated but the Application pool in question is not implemented on the Server that takes over.
Category: Warning
Runs locally: Yes
Created by: Job manager
Available for Event Configuration: Yes
Arguments
| Name | Type | Description |
|---|---|---|
| PrimaryApplicationPoolId | Guid | ID of the primary application pool not implemented as configured on Component configuration. |
| SecondaryApplicationPoolId | Guid | ID of the secondary application pool not implemented as configured in Component configuration. |
__iCore_JobFailed
Created when the execution of a Job fails. Events based on this Event type are not created from child Jobs and/or tracking scopes.
note
If the failed Job has executed as a consequence of an __iCore_JobFailed Event, another __iCore_JobFailed Event will not be created to avoid infinite recursion.
Category: Warning
Runs locally: No
Created by: Worker host manager / Job manager
Available for Event Configuration: Yes
Arguments
| Name | Type | Description |
|---|---|---|
| ErrorMessage | String | The error message from Job. |
| JobId | Int64 | The ID of the failed Job. |
__iCore_JobLost
Created when the state of a Job is changed from 'Running' to 'Lost'. Events of this Event type can be created at Server startup, when a Job is marked as "running" but is not recognized by the Server.
Category: Error
Runs locally: No
Created by: Job manager
Available for Event Configuration: Yes
Arguments
| Name | Type | Description |
|---|---|---|
| JobId | Int64 | The ID of the failed Job. |
__iCore_LicenseExpirationNotification
Created when the license for the iCore Service on a specific server is approaching its expiration date. The purpose is to remind the user to renew the license and reactivate iCore. A warning is also written to the log.
If the license has a valid starting date, a notification will be generated when 10% of the license period remains. If no starting date exists, the notification will be generated when 30 days (or less) of the license remains. When one of these conditions are fulfilled, iCPS creates Events and Log entries once every 24 hours.
Category: Warning
Runs locally: No
Created by: Server monitor
Available for Event Configuration: Yes
Arguments
| Name | Type | Description |
|---|---|---|
| ExpirationDate | DateTime | Date and time when the license expires. |
| Message | String | A message which describes the problem. |
See Also
License
__iCore_ManuallyExecutedComponent
Created when a Component is manually executed from an iCore tool (for example the Run Comp tool).
Category: Information
Runs locally: Yes
Created by: Tool executing the Component (see also property EventSource)
Available for Event Configuration: No
Arguments: No arguments.
__iCore_MaxConcurrentExceeded
Created if the maximum concurrent Jobs allowed for a Component configuration is exceeded. Events of this type can be triggered by a fail-over conflict, for example when two computers lose their connection and both initiate fail-over.
Category: Warning
Runs locally: No
Created by: Job manager
Available for Event Configuration: Yes
Arguments
| Name | Type | Description |
|---|---|---|
| JobId | IList< Int64 > | The IDs of all Jobs executing under Component configuration that has exceeded max concurrent Jobs. |
| ComponentConfigurationId | Guid | ID of the Component configuration that exceeded max concurrent executing Jobs. |
__iCore_NoMatchingEventconfigurationFound
Created when an Event missing a matching Event configuration has been created. A warning or error is also written to the log (see Event type).
note
If an Event configuration for _NoMatchingEventconfigurationFound is missing, another _NoMatchingEventconfigurationFound will not be created (to avoid infinite recursion).
Category: Warning
Runs locally: No
Created by: Event processor
Available for Event Configuration: Yes
Arguments
| Name | Type | Description |
|---|---|---|
| EventId | Int64 | The ID of the Event with no matching Event configuration. |
See also Event configuration
__iCore_RuntimeErrorOccurred
An Event of this Event type is created when a generic error occurs in iCore runtime (when an iCore system fails to perform an operation). When the Event is created, an error log is written by the system, most often to the iCore system log and the OS event log. If errors are generated with a high frequency, one instance of this Event may be created for several errors.
note
This problem can be caused by an internal error in an iCore Server. When this occurs, investigate the system status.
Category: Error
Runs locally: Yes
Created by: All system parts
Available for Event Configuration: Yes
Arguments
| Name | Type | Description |
|---|---|---|
| Errors | List<String> | Error messages from runtime error. One instance of this Event can be created for several errors. If runtime errors are created in high pace these are cached and one Event is created for multiple errors. |
__iCore_ServerpartFailoverCompleted
Created when Server part has been successfully transferred to fail-over Server part.
note
When this occurs, investigate the reason for the fail-over and take suitable action.
Category: Information
Runs locally: Yes
Created by: Server monitor
Available for Event Configuration: Yes
Arguments
| Name | Type | Description |
|---|---|---|
| ServerPart | ServerPartType | The server part type that fail-over was completed for. |
| Succeeded | Bool | True if fail-over was successful, otherwise false. |
See Also
__iCore_ServerpartFailoverStarted
Servers and Server parts
__iCore_ServerpartFailoverStarted
An Event of this Event type is created when fail-over is initiated by the iCore system. An Event is not created if a Server part is moved manually with iCore tools. This Event is followed by a _ServerpartFailoverCompleted Event.
note
When this occurs, investigate the reason for the fail-over and take suitable action.
Category: Information
Runs locally: Yes
Created by: Server monitor
Available for Event Configuration: Yes
Arguments
| Name | Type | Description |
|---|---|---|
| ServerPart | ServerPartType | The type of Server part starting a failover. |
See also
_ServerpartFailoverCompleted
Servers and Server parts
__iCore_ServerPartFaulted
An Event of this Event type is created when a Server part enters the faulted state, which is a terminal state that indicates an abnormal condition caused by an unexpected error in the service runtime.
This Event can be used to send alarm notifications to an operator to investigate the problem.
note
Depending on circumstances of the failure (which Server part was involved, and the nature of the failure), the Event may not always be generated or processed correctly.
Category: Error
Runs locally: Yes
Created by: Server monitor
Available for Event Configuration: Yes
Arguments
| Name | Type | Description |
|---|---|---|
| ServerPart | ServerPartType | The type of Server part that faulted. |
| ErrorMessage | String | An error message describing the cause of the failure. |
| MachineId | String | The hostname of the computer on which the Server part was running. |
| WorkerHostProcessIds | Int32[] | The process IDs of all the worker host processes that were running at the time of the failure associated with this Server. |
| ServiceProcessId | Int32 | The process ID of the service process. |
| SystemId | Int32 | The ID of the iCore system. |
| SystemName | String | The name of the iCore system. |
See also
Servers and Server parts
__iCore_SessionJobDiscontinued
note
Created when a session Job ends abruptly and the maximum restart count has been reached.
The session Job will not be recreated during the current session. The iCore system must be restarted to create a new Job of this Component configuration. It is recommended to troubleshoot the failing Job.
Category: Warning
Runs locally: No
Created by: Job manager
Available for Event Configuration: Yes
Arguments
| Name | Type | Description |
|---|---|---|
| Reason | String | The reason for the Session job discontinuation. |
| ComponentConfigurationId | Guid | The ID of the Component configuration for the Job. |
| JobId | Int64 | The ID of the Job. |
__iCore_SystemSessionCreated
Created during system startup, before any other processing is done.
Category: Information
Runs locally: –
Created by: Job manager
Available for Event Configuration: No
Arguments
| Name | Type | Description |
|---|---|---|
| SessionEventId | Int64 | The ID of session Event created. |
__iCore_SystemStarted
Created when all vital server parts are available. Only fired once per session.
note
Use this Event type for Components that are meant to run during the entire system session.
note
If a __iCore_SystemStarted Event is not processed by the Event Processor during the session in which it was created, it will be discarded in the next session.
note
Any Jobs created from an __iCore_SystemStarted that for any reason are not executed in the session will automatically transition to the failed state without ever executing, in other words no Job directly created by __iCore_SystemStarted will ever execute in another session. Any child Events created by a Job that was started by an __iCore_SystemStarted Event will be processed in current session or later sessions, with no restrictions.
Category: Information
Runs locally: No
Created by: Job manager
Available for Event Configuration: Yes
Arguments: -
See Also
Component configuration
__iCore_TrackingScopeCreated
Created when a new tracking scope is created as a child Job.
note
This Event type is for internal iCore use only. It cannot be used in Event Configurations.
Category: Information
Runs locally: –
Created by: Worker host
Available for Event Configuration: No
Arguments: -
__iCore_WorkerHostStarted
Created when a worker host process is started by the Worker Host Manager or Worker Host. For internal use only.
Category: Information
Runs locally: –
Created by: Worker host manager / System Event Processor
Available for Event Configuration: No
Arguments:
| Name | Type | Description |
|---|---|---|
| WorkerId | Int64 | System internal instance ID of the worker started. |
| ProcessId | Int64 | ID of the OS process. |
| ServerId | Guid | ID of the Server on which the process was started. |
| WorkerType | DispatchWorkerType | Type of worker host started. |
| IsSepProcess | Bool | True if the started process is a System event processor managed process. |
See Also
Event configuration
Servers and Server parts
Component configuration