![]() |
![]() |
|
|
EVENTS(5)
Name
EVENTS - list of system-generated events
Description
The System Event Monitor feature detects and reports certain pre-defined events, primarily failures, that a system operator should be aware of. Each event report is an FML32 buffer containing generic fields that describe the event plus other fields that describe the object associated with the event.
The BEA Tuxedo system periodically checks system capacities. If the system finds that a resource is exhausted or near capacity, it posts a system WARN or ERROR event. The system will continue to post these events until the condition subsides.
This reference page first defines the generic event reporting fields, and then lists all system events detected in the current BEA Tuxedo release. System event names begin with a dot ( . ).
Limitations
Event reporting is currently limited to classes defined in TM_MIB(5). Event reporting uses the MIB information base. See MIB(5) and TM_MIB(5) for a definition and the availability of "local attributes," and be aware that the availability of a local attribute depends on the state of communication within the application's network.
It is possible that the system will not post an event related to a system capacity limit (for example, .SysMachineFullMaxgtt) if the condition only exists for a very short period of time.
Generic Event Reporting Fields
Event Lists
T_ACLPERM Event List
T_DOMAIN Event List
no new clients can join the application
T_GROUP Event List
T_MACHINE Event List
T_BRIDGE Event List
T_SERVER Event List
T_SERVICE Event List
.SysServiceTimeout
T_CLIENT Event List
T_TRANSACTION Event List
T_EVENT Event List
Files
${TUXDIR}/udataobj/evt_mib
See Also
![]() |
![]() |
![]() |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|