Table 76 describes the properties that monitor topic messages can contain. Each monitor message can have a different set of these properties.
Table 76 Message properties Type of connection that generated the event. This property can have the following values:
●
●
●
●
●
● FT (connection to fault-tolerant server)
● The type of monitoring event (that is, the last part of the topic name without the $sys.monitor). The reason the event occurred (usually an error). The values this property can have are described in Table 78. When the full message is to be included for message monitoring, this field contains the message as a byte array. You can use the createFromBytes method (in the various client APIs) to recover the message.
● Name of the source object involved with the event. This property can have the following values:
● XID (global transaction ID)
● connections (number of connections)
● unknown (unknown name)
● the name of the user, or anonymous Source object that was involved with the event. This property can have the following values:
●
●
●
●
●
●
●
●
●
●
●
●
● limits (a limit, such as a memory limit)
● Whether the target object is the admin connection. Name of the object that was the target of the event. This property can have the following values:
● XID (global transaction ID)
● connections (number of connections)
● unknown (unknown name)
● the name of the user, or anonymous
● channel (multicast channel) The general object that was the target of the event. This property can have the following values:
●
●
●
●
●
●
●
●
●
●
●
●
● limits (a limit, such as a memory limit)
● Value of the object that was the target of the event, such as the name of a topic, queue, permission, and so on.
Table 77 Event Action Property Values administrator manually committed an XA transaction administrator manually rolled back an XA transaction stored messages rise above a destination’s limit, engaging the flow control feature stored messages fall below a destination’s limit, disengaging the flow control feature administrator manually committed a local transaction administrator manually rolled back a local transaction an application has joined (that is, added) a resource to an existing transaction an application resumed a suspended XA transaction an application called recover (to get a list of XA transactions)
Table 78 Event Reason Property Values The fault-tolerant backup server has disconnected. For message monitoring, this value signifies a message was sent or acknowledged by a consumer. For all other cases, this value signifies a dynamic topic or queue created for a consumer. The oldest message on the destination has been discarded to make room for a new message. This occurs when overflowPolicy=discardOld is set on the destination and either the maxmsgs and/or maxbytes limit set for the destination has been exceeded. Message has exceeded the maxRedelivery count for the queue. For message monitoring, this value signifies a message was posted by a producer. For all other cases, this value signifies a dynamic topic or queue created for a producer. The connection to the server has been reestablished. For message monitoring, this value signifies a message was sent or received from a route. For all other cases, this value signifies a dynamic topic or queue created for a route.
Copyright © TIBCO Software Inc. All Rights Reserved.