Transaction limits event

The TransactionLimitEvent sends an email notification when the number of outstanding transaction objects exceeds 90 percent of the available objects. There is a limit of approximately 65,000 transaction objects. New transactions are blocked with an error message that there is no space for the transactions array.

This event notifies you when 90 percent (approximately 59,000) of the transaction objects are in use, and also provides information about the oldest transaction. A sample email follows:

NPS system nzhost - current number (59000) of transactions exceeded 90% 
of total limit at 30-Aug-11, 14:00:59 EDT.

Oldest Active Transaction:

txid: 0x4eeba
Session id: 101963
PID: 19760
Database: system
User: admin
Client IP: 127.0.0.1
Client PID: 19759
Transaction start date: 2011-08-30 10:55:08

To reduce the outstanding transaction count you may want to consider 
completing/aborting the above transaction.

The number of transaction objects in use can drop by the completion of active transactions, but if the problem relates to older transactions that have not been cleaned up, you can abort the oldest session. In addition, you can use the nzsession -activeTxn command to identify the active transactions. You can identify and abort the older transactions as necessary to free the transaction objects. (You can also stop and restart the software to clean up the transactions.)

Note: The notification repeats every three hours if the object count remains above 90 percent, or when the object count drops below 85 percent but later reaches 59,000 again.

The following table lists the output of the transaction limit event.

Table 1. TransactionLimitEvent rule
Argument	Description	Examples
curNumTX	Specifies the current number of transaction objects which are in use.