Events

Events can be monitored for and used to trigger actions automatically.

Note: In IBM® Spectrum Symphony Developer Edition, events are logged to the log files in the logs directory; it is only in IBM Spectrum Symphony that events use the IBM Spectrum Symphony event framework.
IBM Spectrum Symphony events are categorized as follows:
  • EGO system events, which identify host- and service-related events within the cluster.
  • SOAM system events, which identify session-manager related events within the cluster.
  • Application events, which identify events that affect workload.
  • Cluster management console events, which identify events that affect the web server or the cluster management console itself.
  • REST events, which identify events that affect the REST web server.

By default, events are not enabled. If you want to be notified about application events, enable the event framework. Note that even if the event framework is not enabled, you can monitor events using the log files in the logs directory.

EGO system events

Table 1. EGO system event details
Event name Default level Scenario when this event triggers Description
SYS_HOST_CLOSED
  • Component name: ego_vemkd
  • Returned integer: 6
 Informational A host is closed. Host <host_name> has become closed in cluster <cluster_name>.
SYS_HOST_CLOSED_RECLAIM
  • Component name: ego_vemkd
  • Returned integer: 15
 Warning A host in the cluster becomes closed_reclaim. Host <host_name> has been closed and its work will be reclaimed in cluster <cluster_name>.
SYS_HOST_UNAVAIL
  • Component name: ego_vemkd
  • Returned integer: 4
 Informational A host becomes unavailable. Host <host_name> has become unavailable in cluster <cluster_name>.
SYS_PEM_DOWN
  • Component name: ego_lim
  • Returned integer: 2
 Error Local PEM goes down. System daemon PEM is down on host <host_name> in cluster <cluster_name>.
SYS_PEM_ROOT_REX_DENIED
  • Component name: ego_pem
  • Returned integer: 17
 Error Starting activity as root is denied. Setting the <activity_name> activity failed because the execution account <account_name> for user ID <user_ID> does not have permission to start the activity using the start command <command_name>.
SYS_PEM_UP
  • Component name: ego_pem
  • Returned integer: 13
 Informational Local pem is started. System daemon PEM is available on host <host_name> in cluster <cluster_name>.
SYS_SLOT_UNDER_MINIMUM
  • Component name: ego_vemkd
  • Returned integer: 16
 Warning Number of slots allocated to a consumer is less than the configured minimum. Consumer <consumer_ID> is currently allocated <current_allocation>, which is less than the configured minimum allocation of <minimum_allocation> number of slots for cluster <cluster_name>.
SYS_SVC_DOWN
  • Component name: ego_sc
  • Returned integer: 7
 Error An EGO service is unavailable. Service <service_name> is no longer available in cluster <cluster_name>.
SYS_SVC_FROZEN
  • Component name: ego_sc
  • Returned integer: 19
 Warning An EGO service is frozen. Service <service_name> is frozen in cluster <cluster_name>.
SYS_SVC_INST_DOCKER_DAEMON_DOWN Error A Dockerized service instance is in the FINISH state because the Docker daemon is down. Service instance <service_name:service_instance_id > on host <host_name> in cluster <cluster_name> failed because the Docker daemon is down. Make sure the Docker daemon is running on the host.
SYS_SVC_INST_DOWN
  • Component name: ego_sc
  • Returned integer: 9
 Error An instance of an EGO service is unavailable. Service instance <service_instance_name> is no longer available on host <host_name> in cluster <cluster_name>.
SYS_SVC_INST_FAILOVER_FAIL
  • Component name: ego_sc
  • Returned integer: 21
 Error An EGO service instance could not fail over.
  1. Service instance service_instance_name on host <host_name> in cluster <cluster_name> could not fail over because fencing for the service instance failed.
  2. Service instance <service_instance_name> on host <host_name> in cluster <cluster_name> could not fail over because fencing could not complete before the wait period expired.
  3. Service instance <service_instance_name> on host <host_name> in cluster <cluster_name> could not fail over because fencing completed with a value other than zero.
SYS_SVC_INST_START_FAIL
  • Component name: ego_sc
  • Returned integer: 20
 Error An EGO service instance cannot start up. Service instance <service_instance_name> could not start up after <retry_amount> retries on host <host_name> in cluster <cluster_name>.
SYS_SVC_INST_STOP
  • Component name: ego_sc
  • Returned integer: 18
 Informational An EGO service is stopped by an administrator. An administrator stopped service instance <service_instance_name> on host <host_name> in cluster <cluster_name>.
SYS_SVC_INST_UP
  • Component name: ego_sc
  • Returned integer: 10
 Informational An instance of an EGO service is started. Service instance <service_instance_name> started or restarted on host <host_name> in cluster <cluster_name>.
SYS_SVC_UP
  • Component name: ego_sc
  • Returned integer: 8
 Informational An EGO service is started. Service <service_name> started or restarted in cluster <cluster_name>.
SYS_VEMKD_CFG_ERROR
  • Component name: ego_vemkd
  • Returned integer: 12
 Error A configuration error prevents VEMKD from starting. System daemon VEMKD exited due to a fatal configuration error.
SYS_VEMKD_DOWN
  • Component name: ego_lim
  • Returned integer: 1
 Error VEMKD is unavailable. System daemon VEMKD is unavailable on host <host_name> in cluster <cluster_name>.
SYS_VEMKD_UP
  • Component name: ego_vemkd
  • Returned integer: 11
 Informational VEMKD is started. System daemon VEMKD is available on host <host_name> in cluster <cluster_name>.

SOAM system events

Table 2. SOAM system event details
Event name Default level Scenario when this event triggers Description
SYS_BM_BOUNDARY_BREACHED
  • Component name: SYM
  • Returned integer: 75025
 Warning The session manager memory usage exceeds the threshold (in percentage). The boundary event <event_name> was triggered for the boundary element <element_name> because its value reached <threshold> for process <process_name> on host <host_name>.
SYS_DS_READFAIL_CDU
  • Component name: SYM
  • Returned integer: 75066
 Error The session manager failed to read from data storage. Session <session_ID> of application <application_name> failed because it is unable to read common data update information <information> from storage due to <reason>. Resolve the problem with the storage medium.
SYS_DS_READFAIL_JOURNALEXT_SESSION
  • Component name: SYM
  • Returned integer: 75077
 Session <session_ID> of application <application_name> will abort because it is unable to read journal extension information from storage due to <reason>. Resolve the problem with the storage medium.
SYS_DS_READFAIL_JOURNALEXT_TASK
  • Component name: SYM
  • Returned integer: 75079
 Task <task_ID> of session <session_ID> of application <application_name> failed because it is unable to read journal extension information from storage due to <reason>. Resolve the problem with the storage medium.
SYS_DS_READFAIL_SESSION
  • Component name: SYM
  • Returned integer: 75028
 Session <session_ID> of application <application_name> will abort because it is unable to read common data information from storage due to <reason>. Resolve the problem with the storage medium.
SYS_DS_READFAIL_TASKINPUT
  • Component name: SYM
  • Returned integer: 75029
 Task <task_ID> of session <session_ID> of application <application_name> failed because it is unable to read input data from storage due to <reason>. Resolve the problem with the storage medium.
SYS_DS_READFAIL_TASKOUTPUT
  • Component name: SYM
  • Returned integer: 75030
 Task <task_ID> of session <session_ID> of application <application_name> failed because it is unable to read output data from storage due to <reason>. Resolve the problem with the storage medium.
SYS_DS_WRITEFAIL_CDU
  • Component name: SYM
  • Returned integer: 75067
 Warning The session manager failed to write to data storage. Session <session_ID> of application <application_name> is unable to write common data update information <information> into storage due to <reason>. The write operation will be retried later. Increase the amount of storage space.
SYS_DS_WRITEFAIL_CDU_OBJECT
  • Component name: SYM
  • Returned integer: 75068
 Common data update <update> of session <session_ID> of application <application_name> is unable to write itself into storage due to <reason>. The write operation will be retried later. Increase the amount of storage space.
SYS_DS_WRITEFAIL_SESSION
  • Component name: SYM
  • Returned integer: 75031
 Session <session_ID> of application <application_name> is unable to write common data into storage due to <reason>. The write operation will be retried later. Increase the amount of storage space.
SYS_DS_WRITEFAIL_SESSION_METACONFIG_OBJECT
  • Component name: SYM
  • Returned integer: 75038
 The session is unable to write session tag <tag_name> to storage due to <reason>. The write operation will be retried later. Increase the amount of storage space.
SYS_DS_WRITEFAIL_SESSION_OBJECT
  • Component name: SYM
  • Returned integer: 75034
 Session <session_ID> of application <application_name> is unable to write itself into storage due to <reason>. The write operation will be retried later. Increase the amount of storage space.
SYS_DS_WRITEFAIL_TASKINPUT
  • Component name: SYM
  • Returned integer: 75032
 Task <task_ID> of session <session_ID> of application <application_name> is unable to write input data into storage due to <reason>. The write operation will be retried later. Increase the amount of storage space.
SYS_DS_WRITEFAIL_TASKOUTPUT
  • Component name: SYM
  • Returned integer: 75033
 Task <task_ID> of session <session_ID> of application <application_name> is unable to write output data into storage due to <reason>. The write operation will be retried later. Increase the amount of storage space.
SYS_DS_WRITEFAIL_TASK_OBJECT
  • Component name: SYM
  • Returned integer: 75035
 Task <task_ID> of session <session_ID> of application <application_name> is unable to write itself into storage due to <reason>. The write operation will be retried later. Increase the amount of storage space.
SYS_DS_WRITEFAIL_JOURNALEXT_SESSION
  • Component name: SYM
  • Returned integer: 75076
 Error The session manager failed to write to data storage. Session <session_ID> of application <application_name> is unable to write journal extension information into storage due to <reason>. The write operation will be retried later. Increase the amount of storage space.
SYS_DS_WRITEFAIL_JOURNALEXT_TASK
  • Component name: SYM
  • Returned integer: 75078
 Task <task_ID> of session <session_ID> of application <application_name> is unable to write its journal extension information into storage due to <reason>. The write operation will be retried later. Increase the amount of storage space.
SYS_FAILOVER_RETRIED
  • Component name: SYM
  • Returned integer: 75001
 Informational Trying to restart the session manager or service instance manager. Restart the IBM Spectrum Symphony daemon <daemon_name> with ID <ID>.
SYS_SIM_DOWN
  • Component name: SYM
  • Returned integer: 75007
 Error The service instance manager goes down abnormally SIM <SIM_ID> with process ID <process_ID> for application <application_name> exited from host <host_name>.
SYS_SSM_DOWN
  • Component name: SYM
  • Returned integer: 75003
 Error The session manager goes down abnormally. Session manager process <process_ID> exited from host <host_name>.
SYS_SSM_DOWN_NORMAL
  • Component name: SYM
  • Returned integer: 75036
 Informational The session manager goes down normally. Session manager process <process_ID> exited from host <host_name>.
SYS_SSM_UP
  • Component name: SYM
  • Returned integer: 75002
 Informational The session manager comes up. Session manager process <process_ID> started on host <host_name>.
SYS_VEM_START_CONTAINER_FAILED
  • Component name: SYM
  • Returned integer: 75090
 Error The system is unable to call the vem_startcontainer API. Unable to call vem_startcontainer() due to: <reason>, for consumer <consumer_name>, command <command_name>, workDir <directory_name>, env <environment>, and host <host_name>.

Application events

Table 3. Application event details
Event name Default level Scenario when this event triggers Detailed description
SOA_APPLICATION_PROFILE_UPDATE
  • Component name: SYM
  • Returned integer: 75069
 Informational An application profile is updated. Domain <Application>: Application <application_name>: The application profile updated successfully.
SOA_APPLICATION_SIM_OSTYPE_MISS
  • Component name: SYM
  • Returned integer: 75039
 Error A host is blocked because its operating system type is not defined in the SIM section of the application profile. Application <application_name>: IBM Spectrum Symphony received a resource (host: <host_name>) with operating system type: <operating_system>. This operating system type has not been defined as a valid resource in the SIM section of the application profile. Host <host_name> has been blocked for this application.
SOA_APPLICATION_SIM_START_FAILED
  • Component name: SYM
  • Returned integer: 75080
 Error A SIM fails to start. Application <application_name>: Host <host_name> is blocked because the service instance manager can not successfully start up, and the attribute blockHostOnTimeout is set to true in the application profile.
SOA_APPLICATION_SIM_START_TIMEOUT
  • Component name: SYM
  • Returned integer: 75065
 Error The timeout for a service instance manager to start up has expired. Application <application_name>: Host <host_name> is blocked because the service instance manager timed out while starting up, and the attribute blockHostOnTimeout is set to true in the application profile.
SOA_APPLICATION_SSM_OSTYPE_MISS
  • Component name: SYM
  • Returned integer: 75040
 Error A host is newly added but its operating system type is not defined in the SSM section of the application profile. Application <application_name>: IBM Spectrum Symphony received a resource (host: host_name>) with operating system type: <operating_system>. This operating system type has not been defined as a valid resource in the SSM section of the application profile.
SOA_DEBUG_SERVICE_EVENT_REPLAY
  • Component name: SYM
  • Returned integer: 75064
 Warning The Service debugSetting="customized" and a service event occurs for which the debug action is to write service event replay files. Application <application_name>: SIM detected <error> for method <method_name>. Debug action is <action_name>. Serl file is <file_name>.
SOA_INVOKE_EXIT
  • Component name: SYM
  • Returned integer: 75047
 Error An Invoke method exits. Application <application_name>, service <service_name>: Method <method_name> exited.

Action on workload: action <action_name> taken on task <task_ID> in session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_name>, host <host_name>, service <service_name>.
SOA_INVOKE_FAILURE
  • Component name: SYM
  • Returned integer: 75050
 Error An Invoke method throws a failure exception. Application <application_name>, service <service_name>: Failure exception thrown on method <method_name>, control code <control_code>.

Action on workload: action <action_name> taken on task <task_ID> in session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name>.
SOA_FAILED_TO_ACCEPT_CLIENT
  • Component name: SYM
  • Returned integer: 75089
 Error The OS communication system returns an error while attempting to accept a new client's connection. SSM received an OS communication system error while accepting new client. EVENT_SOA_FAILED_TO_ACCEPT_CLIENT. Accepting address IP_address, system error error_ID.
SOA_INVOKE_FATAL_ERROR
  • Component name: SYM
  • Returned integer: 75053
 Error An Invoke method throws a fatal exception. Application <application_name>, service <service_name>: Fatal exception thrown on method <method_name>, control code <control_code>.

Action on workload: action <action_name> taken on task <task_ID> in session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name>.
SOA_INVOKE_RETURN
  • Component name: SYM
  • Returned integer: 75041
 Informational An Invoke method returns. Application <application_name>, service <service_name>: Successful return on method <method_name>, control code <control_code>.

Action on workload: action <action_name> taken on task <task_ID> in session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name.
SOA_INVOKE_TIMEOUT
  • Component name: SYM
  • Returned integer: 75044
 Error The timeout for an Invoke method has expired. Application <application_name>, service <service_name>: Method <method_name> timed out after <duration> seconds.

Action on workload: action <action_name> taken on task <task_ID> in session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name.
SOA_OTHERS_EXIT
  • Component name: SYM
  • Returned integer: 75049
 Error A Register, CreateService, or SessionLeave method exits. Application <application_name>, service <service_name>: Method <method_name> exited.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name.
SOA_OTHERS_FAILURE
  • Component name: SYM
  • Returned integer: 75052
 Error A CreateService or SessionLeave method throws a failure exception. Application <application_name>, service <service_name>: Failure exception thrown on method <method_name>, control code <control_code>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name.
SOA_OTHERS_FATAL_ERROR
  • Component name: SYM
  • Returned integer: 75055
 Error A CreateService or SessionLeave method throws a fatal exception. Application <application_name>, service <service_name>: Fatal exception thrown on method <method_name>, control code <control_code>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name.
SOA_OTHERS_RETURN
  • Component name: SYM
  • Returned integer: 75043
 Informational A CreateService or SessionLeave method returns. Application <application_name>, service <service_name>: Successful return on method <method_name>, control code <control_code>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name.
SOA_OTHERS_TIMEOUT
  • Component name: SYM
  • Returned integer: 75046
 Error The timeout for a Register, CreateService, or SessionLeave method has expired. Application <application_name>, service <service_name>: Method <method_name> timed out after the configured <duration> seconds.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name.
SOA_RS_EXIT_PORT
  • Component name: SYM
  • Returned integer: 75061
 Error Repository service exited due to the configured listening port being in use or not valid. Domain <Application>: The repository service exited because it failed to accept requests on the configured port <port> on host <host_name>. Reason: <reason>. Change the port number in the appropriate configuration file and try again. For more details, refer to the IBM Spectrum Symphony error messages reference.
SOA_RS_EXIT_STORAGE_DIR
  • Component name: SYM
  • Returned integer: 75062
 Error Repository service exited due to its failure to access the configured storage directory. Domain <System, Application>: The repository service exited because it cannot access its storage directory <directory_name> from host <host_name> running as user <user_name>. For more details, refer to the IBM Spectrum Symphony error messages reference.
SOA_RS_STARTED
  • Component name: SYM
  • Returned integer: 75063
 Informational The repository service has started. Domain <SOAM>: The repository service started successfully on host <host_name>. Listening on port <port>.
SOA_SD_EXIT_ADMIN_PORT
  • Component name: SYM
  • Returned integer: 75058
 Error Session director exited due to the configured listening administrative port being in use or not valid. Domain <Application>: The session director exited because it failed to accept administrative requests on the configured port <port> on host <host_name>. Reason: <reason>. Change the port number in the appropriate configuration file and try again. For more details, refer to the IBM Spectrum Symphony error messages reference.
SOA_SD_EXIT_PROFILES_DIR
  • Component name: SYM
  • Returned integer: 75059
 Error Session director SD exited due to its failure to access the configured directory for storing application profiles. Domain <System, Application>: Session director has exited because it cannot access the application profile directory <directory_name> from host <host_name> running as user <user_name>. Reason: <reason>. For more details, refer to the IBM Spectrum Symphony error messages reference.
SOA_SD_EXIT_SDK_PORT
  • Component name: SYM
  • Returned integer: 75057
 Error Session director exited due to the configured listening SDK port being in use or not valid. Domain <Application>: Session director has exited because it failed to accept client connections on the configured port <port> on host <host_name>. Reason: <reason>. Change the port number in the appropriate configuration file and try again. For more details, refer to the IBM Spectrum Symphony error messages reference.
SOA_SD_STARTED
  • Component name: SYM
  • Returned integer: 75060
 Informational The session director service has started. Domain <SOAM>: Session director started successfully on host <host_name>. Listening on administrator port <port> and SDK port <port>.
SOA_SERVICE_BLOCKED
  • Component name: SYM
  • Returned integer: 75013
 Error An application is blocked from receiving slots on a host Application <application_name>: Host <host_name> is blocked due to service instance <service_instance_ID> with process ID <process_ID>. Reason: <reason>.
SOA_SERVICE_DEPLOYMENT_FAILED
  • Component name: SYM
  • Returned integer: 75037
 Error A service failed to deploy. Application <application_name>: the service <service_name> could not be deployed to host <host_name>. The logged error was: <error>.
SOA_SERVICE_INIT_FAILED
  • Component name: SYM
  • Returned integer: 75008
 Error A service instance creation failed. Application <application_name>: failed to create service <service_name> on host <host_name>.
SOA_SESSIONENTER_EXIT
  • Component name: SYM
  • Returned integer: 75048
 Error A SessionEnter method exits. Application <application_name>, service <service_name>: Method <method_name> exited.

Action on workload: action <action_name> taken on session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_name>, host <host_name>, service <service_name>.
SOA_SESSIONENTER_FAILURE
  • Component name: SYM
  • Returned integer: 75051
 Error A SessionEnter method throws a failure exception. Application <application_name>, service <service_name>: Failure exception thrown on method <method_name>, control code <control_code>.

Action on workload: action <action_name> taken on session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name>.
SOA_SESSIONENTER_FATAL_ERROR
  • Component name: SYM
  • Returned integer: 75054
 Error A SessionEnter method throws a fatal exception. Application <application_name>, service <service_name>: Fatal exception thrown on method <method_name>, control code <control_code>.

Action on workload: action <action_name> taken on session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name>.
SOA_SESSIONENTER_RETURN
  • Component name: SYM
  • Returned integer: 75042
 Informational A SessionEnter method returns. Application <application_name>, service <service_name>: Successful return on method <method_name>, control code <control_code>.

Action on workload: action <action_name> taken on session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name>.
SOA_SESSIONENTER_TIMEOUT
  • Component name: SYM
  • Returned integer: 75045
 Error The timeout for a SessionEnter method has expired. Application <application_name>, service <service_name>: Method <method_name> timed out after the configured <duration> seconds.

Action on workload: action <action_name> taken on session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name>.
SOA_SESSIONUPDATE_EXIT
  • Component name: SYM
  • Returned integer: 75073
 Error An onSessionUpdate method exits. Application <application_name>, service <service_name>: Method <method_name> exited.

Action on workload: action <action_name> taken on session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name>.
SOA_SESSIONUPDATE_FAILURE
  • Component name: SYM
  • Returned integer: 75074
 Error An onSessionUpdate method throws a failure exception. Application <application_name>, service <service_name>: Failure exception thrown in method <method_name>, control code <control_code>.

Action on workload: action <action_name> taken on session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name>.
SOA_SESSIONUPDATE_FATAL_ERROR
  • Component name: SYM
  • Returned integer: 75075
 Error An onSessionUpdate method throws a fatal exception. Application <application_name>, service <service_name>: Fatal exception thrown in method <method_name>, control code <control_code>.

Action on workload: action <action_name> taken on session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name>.
SOA_SESSIONUPDATE_RETURN
  • Component name: SYM
  • Returned integer: 75071
 Error An onSessionUpdate method returns. Application <application_name>, service <service_name>: Successful return on method <method_name>, control code <control_code>.

Action on workload: action <action_name> taken on session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name>.
SOA_SESSIONUPDATE_TIMEOUT
  • Component name: SYM
  • Returned integer: 75072
 Error The timeout for an onSessionUpdate method has expired. Application <application_name>, service <service_name>: Method <method_name> timed out after the configured <duration> seconds.

Action on workload: action <action_name> taken on session <session_ID>.

Action on service instance: action <action_name> taken on service instance process <process_ID>, host <host_name>, service <service_name>.
SOA_SESSION_ABORTED
  • Component name: SYM
  • Returned integer: 75017
 Error A session is aborted. Application <application_name>: session <session_ID> aborted with reason <reason>.
SOA_SESSION_LOST
  • Component name: SYM
  • Returned integer: 75015
 Warning A connection to the session is lost. Application <application_name>: session manager process <process_ID> on host <host_name> detected a connection lost from the session <session_ID>.
SOA_SESSION_PRI_CHANGED
  • Component name: SYM
  • Returned integer: 75020
 Informational The priority of a session is changed and the session is resumed. Application <application_name>: the priority of session <session_ID> changed from <old_priority> to <new_priority>.
SOA_SESSION_RESUMED
  • Component name: SYM
  • Returned integer: 75019
 Informational A session is resumed. Application <application_name>: session <session_ID> resumed with reason <reason>.
SOA_SESSION_SUSPENDED
  • Component name: SYM
  • Returned integer: 75018
 Warning A session is suspended. Application <application_name>: session <session_ID> suspended with reason reason.
SOA_SESSION_TIMEOUT
  • Component name: SYM
  • Returned integer: 75084
 Warning The session timeout has been reached. Session <session_ID> in application <application_name> timeout. The session timeout is <value>. Session create time was <time_stamp> and current time is <time_stamp>.
SOA_TASK_CANCELLED
  • Component name: SYM
  • Returned integer: 75056
 Warning A task is cancelled. Application <application_name>: task task_ID of session <session_ID> terminated with reason reason.
SOA_TASK_EXECUTION_TIMEOUT
  • Component name: SYM
  • Returned integer: 75085
 Warning The task timeout has been reached. Task <task_ IDtask ID in session <session_ID> in application <application_name> timeout. The task execution timeout is <value>. Task submit time was <time_stamp> and current time is <time_stamp>.
SOA_TASK_PRI_CHANGE
  • Component name: SYM
  • Returned integer: 75081
 Informational The priority of a session is updated. Application application_name: session ID session_ID, task ID task_ID is being updated from priority old_priority to priority hew_priority."
SOA_TASK_PRI_NO_TASK
  • Component name: SYM
  • Returned integer: 75082
 Warning There is no task with the specified ID in the session while the task is in RUNNING or PENDING state. Domain <SOAM>: No task with ID task_ID in session session_ID: task_ID found in RUNNING or PENDING state. Specify another task ID, or check the state of task session_ID:task_ID:task_ID.
SOA_TASK_PRI_NOT_TPS_SESSION
  • Component name: SYM
  • Returned integer: 75083
 Informational Unable to update task with the specified ID in the session because the session is a non-TPS session and the task in this session has no priority. Unable to update task with ID task_ID in session session_ID, application application_name because the session session_ID is a non-TPS session and the task in this session has no priority.

Cluster management console events

Table 4. Cluster management console event details
Event name Default level Scenario when this event triggers Detailed description
SYS_GUI_CPU_HI_WATER_MARK
  • Component name: GUI
  • Returned integer: 3
 Warning The web server host utilization exceeds the threshold set for CPU_HIGH_MARK in wsm.conf. Web server CPU usage <CPU_usage> reached its threshold of <CPU_threshold> on host <host_name> in cluster <cluster_name>.
SYS_GUI_MEMORY_HI_WATER_MARK
  • Component name: GUI
  • Returned integer: 2
 Warning The web server memory usage exceeds the threshold set for MEM_HIGH_MARK in wsm.conf. Web server memory usage <memory_usage> reached its threshold of <memory_threshold> on host <host_name> in cluster <cluster_name>.
SYS_GUI_SERVER_DOWN
  • Component name: GUI
  • Returned integer: 1
 Error The cluster management console service exits. The web server on host <host_name> in cluster <cluster_name> is down.
SYS_GUI_SERVER_UP
  • Component name: GUI
  • Returned integer: 0
 Informational The cluster management console service starts. The web server has started on host <host_name> using port <port> in cluster <host_name>.

REST events

Table 5. REST event details
Event name Default level Scenario when this event triggers Detailed description
SYS_REST_CPU_HI_WATER_MARK
  • Component name: REST
  • Returned integer: 3
 Warning The web server host utilization exceeds the threshold set for CPU_HIGH_MARK in wsm.conf. Web server CPU usage <CPU_usage> reached its threshold of <CPU_threshold> on host <host_name> in cluster <cluster_name>.
SYS_REST_MEMORY_HI_WATER_MARK
  • Component name: REST
  • Returned integer: 2
 Warning The web server memory usage exceeds the threshold set for MEM_HIGH_MARK in wsm.conf. Web server memory usage <memory_usage> reached its threshold of <memory_threshold> on host <host_name> in cluster <cluster_name>.
SYS_REST_SERVER_DOWN
  • Component name: REST
  • Returned integer: 1
 Error The REST service exits. The web server on host <host_name> in cluster <cluster_name> is down.
SYS_REST_SERVER_UP
  • Component name: REST
  • Returned integer: 0
 Informational The REST service starts. The web server has started on host <host_name> using port <port> in cluster <host_name>.