Size of transaction pool

Description

The number of Transaction objects that have been created. Whenever a communications request is initiated, either by a client of the Engine or the Engine itself (e.g., when a CIP connection is opened or closed, or when protocol encapsulation is required), a Transaction object for managing that communications request is either taken from the pool or created on the fly. When the transaction is completed, the Transaction object is returned to the pool. Thus, the size of the Transaction pool represents the peak number of concurrent communications requests managed during the lifetime of the

FactoryTalk Linx

process. If this number is continually growing, it may be assumed there is a leak somewhere.