UBR_SRV_COMP_STOP
The event is generated when the Broker detects that a server component has stopped.
UBR_SRV_COMP_STOP Event Header
Field Name | Description |
---|---|
eventCategory | Stop |
eventSeverity |
|
eventTopic | Component |
eventType | 303 |
(Source Fields) | Server component that stopped. |
(Reporter Fields) | Universal Broker that started the component. |
UBR_SRV_COMP_STOP Event Body
Field Name | Notes | Description |
---|---|---|
applProperties | Application-specific properties used for event correlation by UEC. | |
certId | Certificate map identifier that the client certificate was mapped to by the Universal Access Control List cert_map entries. | |
clientCertIssuer | 1, 2 | Issuer field of the digital certificate provided by the client. |
clientCertSerialNo | 1, 2 | Serial number of the digital certificate provided by the client. |
clientCertSubject | 1, 2 | Subject field of the digital certificate provided by the client. |
clientIpAddr | 1 | IP address from which the client's socket connection was established. |
clientPort | 1 | TCP port number from which the client's socket connection was established. |
clientUserId | 1, 3, 4 | User identifier of the client. |
clientWorkId | 1 | Work identifier of the client. |
commandId | Command identifier, specified by the manager, that is used to identify the unit of work. | |
comment | User-provided comment associated with the unit of work. | |
componentId | Component identifier the Broker assigns to the component. | |
elapsedTime | Number of seconds that the server component executed. | |
exitCode | Exit code with which the component ended as reported by the operating system. | |
exitStatus | Final exit status of the component as reported by the operating system. Valid values are:
An abnormal end indicates the component was interrupted by the operating system before it completed processing. Examples of abnormal exits include UNIX signals, Windows exceptions, and z/OS ABENDs. | |
managerFaultTolerant | Specification for whether or not the server component is manager fault tolerant. Possible values are:
| |
pending | Specifies whether or not the server component ended in a PENDING communication state. A PENDING state indicates that the server was running with the Manager Fault Tolerant feature and ended while no manager connection was established with the server. | |
startDateTime | UTC date and time that the server component started. | |
stopDateTime | UTC date and time that the component stopped. |
Notes
- The client information identifies the entity that requested the Broker to start the component. The Broker may have started the component on its own behalf, in which case, the client information identifies the Broker.
- Client digital certificate information is provided only if the client provided a digital certificate.
- A case-dependent value.
- A case-dependent value, but for pre-3.2 clients, the value is always considered case sensitive.