Overview
Attivio is designed to move messages between connectors, API code, components and systems via transports. The Transport classes are designed to provide server side functionality for receiving, processing and returning responses to messages. The default transports are HttpTransport (across machines), JmsTransport (across machines with fault tolerance) and AVMTransport (internal to a single machine). AVM stands for "Attivio Virtual Memory."
The AVM Queue Statistics page provide statistics for the AVM queues within an Attivio system. AVM queues process messages using a proprietary Attivio messaging protocol and are used to provide SEDA messaging within a single Attivio instance. Attivio uses other protocols when sending messages between nodes in a multi-node Attivio installation. Each asynchronous component within and Attivio workflow will have an AVM queue. This diagnostics page allows for analyzing queuing behavior between Attivio components that receive messages on AVM queues.
View incoming links.
AVM Queue Statistics Page Layout
Statistics
The following statistics are provided for each AVM queue.
All AVM queues are Attivio session scope, meaning that they will be reset between Attivio re-starts.
Statistic | Description |
|---|---|
Adds | The number of messages added to a queue. |
Cur Size | The current number of messages in a queue. |
Largest Size | The largest number of messages seen in the queue at any given point in time. |
Avg Size | The average number of messages seen in the queue. |
| Forced Size | Maximum number of messages forced onto a full queue. |
Max Size | The configured maximum size of the queue. |