# Chapter 11. TUXEDO Traps MIB

The TUXEDO system event monitor feature detects and reports certain predefined events - primarily failures that a system operator should be aware of. The TUXEDO SNMP agent on the master node subscribes to all system events and generates a corresponding SNMP trap notification whenever any of these events occur. The enterprise ID used for these traps is `.1.3.6.1.4.1.140.tuxedo`, where `tuxedo` is `300`. For the SNMP agent to receive TUXEDO system events, the TUXEDO system Event Broker (`TMSYSEVT`) must be running as that is the entity that generates the TUXEDO system events.

The Event Traps MIB defines all the traps which will be generated and the objects which are passed in the variable bindings for these traps. The cause and recommended action for each event is described in the following sections.

## Specific Trap Number

Each enterprise-specific trap notification generated by the SNMP agent has a value in the specific trap ID field of the SNMP trap packet which identifies the TUXEDO event. For each trap listed in this chapter, "Trap ID" is the specific trap number that is sent in the trap packet.

## Variable Bindings

SNMP trap notifications generated by the Agent Connection contain 12 variables (attribute/value pairs) in the variable bindings of the trap packet:

`beaEventsDomainId`
  This is the ID of the domain which generated the TUXEDO event notification.

`beaEventsIpcKey`
  This is the IPC key of the TUXEDO domain.

`beaLogicalAgentName`
  The logical agent name of the SNMP agent generating the trap. The executable name is the default logical agent name.

The `tuxEventTrapVars` group contains all objects which are sent as a part of the variable bindings of the traps generated in relation to TUXEDO system events as defined in EVENTS.

### tuxEventsName

> #### Syntax

> `DisplayString`

> #### Access

> not-accessible

> #### Description

> A string that uniquely identifies this event. All system-generated events begin with `.Sys`.

### tuxEventsSeverity

> #### Syntax

> `INTEGER { Error(1), Warn(2), Infor(3) }`

> #### Access

> not-accessible

> #### Description

> Indicates the severity of the system event.

### tuxEventsLmid

> #### Syntax

> `DisplayString` ( `SIZE`(`1..30`) )

> #### Access

> not-accessible

> #### Description

> A string identifying the machine where the event was detected.

### tuxEventsTime

> #### Syntax

> `INTEGER`

> #### Access

> not-accessible

> #### Description

> A long integer containing the event detection time, in seconds, according to the clock on the machine where detection took place.

### tuxEventsUsec

> #### Syntax

> `INTEGER`

> #### Access

> not-accessible

> #### Description

> A long integer containing the event detection time, in microseconds, according to the clock on the machine where detection took place. While the units of this value will always be microseconds, the actual resolution depends on the underlying operating system and hardware.

### tuxEventsDescription

> #### Syntax

> `DisplayString`

> #### Access

> not-accessible

> #### Description

> A one-line string summarizing the event.

### tuxEventsClass

> #### Syntax

> `DisplayString`

> #### Access

> not-accessible

> #### Description

> The class of the object associated with the event. Depending on TA_CLASS, the event notification buffer will contain additional fields specific to an object of this class.

### tuxEventsUlogCat

> #### Syntax

> `DisplayString`

> #### Access

> not-accessible

> #### Description

> Catalog name from which the message was derived, if any.

### tuxEventsUlogMsgNum

> #### Syntax

> `INTEGER`

> #### Access

> not-accessible

> #### Description

> Catalog message number, if the message was derived from a catalog.

### tuxTdomainID

> #### Syntax

> `DisplayString` (`SIZE` (`0..30`))

> #### Access

> not-accessible

> #### Description

> Domain identification string. Refer to Chapter 4, "TUXEDO Core MIB."

### tuxTdomainKey

> #### Syntax

> `INTEGER``(32769..262143)`

> #### Access

> not-accessible

> #### Description

> Numeric key for the well-known address in a TUXEDO System/T bulletin board. In a single processor environment, this key "names" the bulletin board. In a multiple processor or LAN environment, this key names the message queue of the DBBL. In addition, this key is used as a basis for deriving the names of resources other than the well-known address, such as the names for bulletin boards throughout the application. Refer to Chapter 4, "TUXEDO Core MIB."

### beaLogicalAgentName

> #### Syntax

> `DisplayString`

> #### Access

> not-accessible

> #### Description

> The logical name of the agent as provided in the `-l` option (service name in case of Windows NT) when the agent was started. This is the agent which is monitoring this domain. If there are multiple Agent Connection agents running on a managed node, this name needs to be appended to the community with an @ sign to get the MIB values from the appropriate agent. For example, if there are two logical agents, `simp_snmpd` and `bank_snmpd`, the communities used to query values from these agents would be `public@simp_snmpd` and `public@bank_snmpd` respectively. The component after the `@` sign is used to identify the agent to which the MIB query is to be sent.

> This object is passed in the variable binding of all SNMP traps generated on behalf of TUXEDO system events.

> Note: To run multiple Agent Connection agents on the same managed node, they must be started as sub-agents (without `-s` option) and run after starting the Agent Integrator.

## Trap Definitions

This section defines all the traps generated by the TUXEDO SNMP agent when system events occur.

### DOMAIN Traps

The Domain Traps group defines the TUXEDO domain specific event traps.

### resourceConfigTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysResourceConfig` occurs. It denotes a system configuration change.

> #### Action

> This is an informational message.

> #### Trap ID

> 1

### MACHINE Traps

The Machine Traps group defines the TUXEDO machine specific event traps.

### machineBroadcastTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysMachineBroadcast` occurs. It denotes broadcast delivery failure. This message indicates that `tpbroadcast()` failed for at least one accesser on the LMID of the application.

> #### Action

> Since the broadcast messages are sent in no-blocking mode, it is possible that the process doing the broadcasting encountered a blocking condition and dropped a message. Configure larger message queues or load-balance clients and servers such that excessive load is not put on some machines.

> #### Trap ID

> 2

### machineConfigTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysMachineConfig` occurs. It denotes a change in a particular machine configuration.

> #### Action

> This is an informational message.

> #### Trap ID

> 3

### machineFullMaxAccessersTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysMachineFullMaxaccessers` occurs. This message indicates that the given LMID reached the capacity limit on the number of accessers.

> #### Action

> Increase the MAXACCESSERS value for the particular machine. Or, if the hardware/software limits have been reached for the maximum number of users on the machine, move additional users to other machines.

> #### Trap ID

> 4

### machineFullMaxConvTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysMachineFullMaxconv` occurs. This message indicates that the given LMID reached the capacity limit on the number of concurrent conversations.

> #### Action

> Increase the value of MAXCONV for the particular machine to the point that this event is not generated.

> #### Trap ID

> 5

### machineFullMaxGttTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysMachineFullMaxgtt` is raised. This message indicates that the given machine reached the capacity limit on the number of concurrent transactions.

> #### Action

> Increase the value of MAXGTT for the particular machine to the point that this event is not generated.

> #### Trap ID

> 6

### machineFullMaxWsClientsTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysMachineFullMaxwsclients` is raised. This message indicates that the given machine reached the capacity limit on the number of workstation clients.

> #### Action

> Increase the value of MAXWSCLIENTS for the particular machine to the point that this event is not generated.

> #### Trap ID

> 7

### machineMsgQTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysMachineMsgq` occurs. This message indicates that the server posting a message encountered a blocking condition while putting a message on the message queue.

> #### Action

> Configure larger message queues and/or distribute the load equally on all the machines.

> #### Trap ID

> 8

### machinePartitionedTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysMachinePartitioned` occurs. This message indicates that DBBL partitioned the stated machine either because the BBL on the machine is slow or the network link between the master and the machine is broken.

> #### Action

> This can occur due to several reasons:

> - The entire network may be bogged down due to heavy traffic.

> - The BBL or BRIDGE on the non-master is either dead or slow.

> - The BRIDGE process on the non-master is extremely busy.

> The software is capable of unpartitioning the machine if things stabilize.

> #### Trap ID

> 9

### machineSlowTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysMachineSlow` occurs. This message indicates that BBL on the non-master machine is slow in generating IAMOK messages. These messages are sent periodically from BBLs to the DBBL which helps the DBBL maintain the pulse of the system.

> #### Action

> This can occur due to several reasons:

> - The entire network may be bogged down due to heavy traffic.

> - The BBL on the non-master may be either dead or slow.

> - The BRIDGE process on the non-master is extremely busy.

> This problem can be intermittent.

> #### Trap ID

> 10

### machineStateTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysMachineState` occurs. This denotes that a particular machine changed its state.

> #### Action

> This is an informational message.

> #### Trap ID

> 11

### BRIDGE Traps

The Bridge Traps group defines the TUXEDO bridge specific traps.

### networkConfigTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysNetworkConfig` occurs. This message indicates the network link between the two machines specified changed to a new state.

> #### Action

> This is an informational message.

> #### Trap ID

> 12

### networkDroppedTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysNetworkDropped` occurs. This message indicates the network link between the two machines specified was dropped abnormally.

> #### Action

> This can happen either because the BRIDGE on either machine died or one of the machines crashed.

> #### Trap ID

> 13

### networkFailureTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysNetworkFailure` occurs. This indicates a network connection failure between BRIDGE processes.

> #### Action

> This can happen either because the BRIDGE on remote machine died or the remote machine itself crashed.

> #### Trap ID

> 14

### networkFlowTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysNetworkFlow` occurs. This message states that the virtual circuit between machines changed to a new state.

> #### Action

> This is an informational message.

> #### Trap ID

> 15

### networkStateTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysNetworkState` occurs. This message indicates that the server died abnormally and BBL cleaned up the slot allocated by the server.

> #### Action

> Debug the server and fix the problem before it is restarted again.

> #### Trap ID

> 16

### SERVER Event Traps

The Server Traps group defines the TUXEDO server specific traps.

### serverCleaningTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysServerCleaning` occurs. This message indicates that the server died abnormally and BBL cleaned up the slot allocated by the server.

> #### Action

> Debug the server and fix the problem before it is restarted again.

> #### Trap ID

> 17

### serverConfigTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysServerConfig` occurs. This message indicates that the configuration parameters for server have been updated.

> #### Action

> This is an informational message.

> #### Trap ID

> 18

### serverDiedTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysServerDied` occurs. This message indicates that the server died abnormally and the BBL detected this condition in its periodic scan of the BB.

> #### Action

> Debug the server and fix the problem before it is restarted again.

> #### Trap ID

> 19

### serverInitTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysServerInit` occurs. This message indicates that the server specified above failed in `tpsvrinit()` and therefore could not be booted.

> #### Action

> Fix the problem and then reboot the server. This problem might be due to a TUXEDO resource limit or an application-specific problem.

> #### Trap ID

> 20

### serverMaxgenTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysServerMaxgen` occurs. This message indicates that the server died abnormally. Since this has been marked as a restartable server, it has been restarted `MAXGEN-1` times in the specified GRACE period.

> #### Action

> TUXEDO application servers should not die abnormally. If this happens, it is most likely due to an application-specific problem. Debug the server and resolve the problem before restarting it again.

> #### Trap ID

> 21

### serverRestartingTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysServerRestarting` occurs.. This message indicates that the server died abnormally. Since this has been marked as a restartable server, it has been restarted.

> #### Action

> TUXEDO application servers should not die abnormally. If this happens, it is most likely due to an application-specific problem. Debug the server and resolve the problem before restarting it again.

> #### Trap ID

> 22

### serverStateTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysServerState` occurs. This message indicates that the server changed state.

> #### Action

> This is an informational message.

> #### Trap ID

> 23

### serverTpExitTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysServerTpexit` occurs. This message indicates that the server received a request and the service routine code did a `tpreturn(TPEXIT)` while the server was executing application-specific code.

> #### Action

> This is an informational message.

> #### Trap ID

> 24

### CLIENT Traps

The Client Traps group defines the TUXEDO client specific traps.

### clientConfigTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysClientConfig` is raised. This denotes that a particular user on a machine changed its configuration.

> #### Action

> This is an informational message.

> #### Trap ID

> 25

### clientDiedTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysClientDied` occurs. This message indicates that the client exited the application without doing a `tpterm()`. Normally, clients should do a `tpterm()` before exiting the application.

> #### Action

> This is an informational message.

> #### Trap ID

> 26

### clientSecurityTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime,
> tuxEventsUsec, tuxEventsDescription, tuxEventsClass,
> tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysClientSecurity` occurs. This message indicates that the client failed security validation when trying to join the application.

> #### Action

> Check to make sure that this is not an unauthorized user trying to gain access to your application data.

> #### Trap ID

> 27

### clientStateTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysClientState` occurs. This message indicates that a particular client on a machine changed state.

> #### Action

> This is an informational message.

> #### Trap ID

> 28

### TRANSACTION Traps

The Transaction Traps group defines the TUXEDO transaction specific traps.

### transHeuristicAbortTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysTransactionHeuristicAbort` occurs. This message indicates that the database in a particular group performed an heuristic abort on a transaction.

> #### Action

> Check to make sure that the coordinator of the transaction is still running.

> #### Trap ID

> 29

### transHeuristicCommitTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysTransactionHeuristicCommit` occurs. This message indicates that the database in a particular group performed an heuristic commit on a transaction.

> #### Action

> Check to make sure that the coordinator of the transaction is still running.

> #### Trap ID

> 30

### EVENT Traps

The Event Traps group defines the TUXEDO event specific traps.

### eventDeliveryTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysEventDelivery` occurs. This message indicates that the event server failed to perform at least one notification for a posted event.

> #### Action

> Check to make sure that the notifications specified in the subscriptions that match the posted event are doable.

> #### Trap ID

> 31

### eventFailureTrap

> #### Enterprise

> tuxedo

> #### Variables

> `{ tuxEventsName, tuxEventsSeverity, tuxEventsLmid, tuxEventsTime, tuxEventsUsec, tuxEventsDescription, tuxEventsClass, tuxEventsUlogCat, tuxEventsUlogMsgNum, beaDomainId, beaDomainKey, beaLogicalAgentName}`

> #### Description

> This trap is generated when `.SysEventFailure` occurs. The system event server periodically sends a message to itself to detect blocking conditions on the message queues. This event is generated if the server cannot put a message on the queue in no-block mode. It can also be generated if the received message does not match what was sent out earlier. The second possible case is very unlikely. This denotes a system event monitor subsystem failure on a particular host.

> #### Action

> Configure larger message queues or distribute the load in the application equally among all the machines.

> #### Trap ID

> 32