Resolution
goal
What could happen if I continue to enlarge the Consolidator's queue files?
fix
The queue is a memory mapped file, and really large queue files can wreak havoc with available virtual address space. In other words, the Consolidator will start to run out of available chunks of memory addresses in the 2GB of address space that are allowed. In some cases, the queue file size may be increased to as much as 500MB. However, memory allocation failures may result, depending on what kind of fragmentation is occurring.
What could happen if I continue to enlarge the Consolidator's queue files?
fix
The queue is a memory mapped file, and really large queue files can wreak havoc with available virtual address space. In other words, the Consolidator will start to run out of available chunks of memory addresses in the 2GB of address space that are allowed. In some cases, the queue file size may be increased to as much as 500MB. However, memory allocation failures may result, depending on what kind of fragmentation is occurring.
In most cases, having to increase the queue files to that size means that the system is either underpowered or experiencing a prolonged outage of some sort. If it is a prolonged outage, the data will get saved on the agents until connectivity is restored. If the system is underpowered, a larger queue will just mask the real problem for a short while.
For more information about Consolidator's queue file, please read the following Knowledge Base Article:
NETIQKB2047 Error: 'The Consolidator's incoming communications queue is full.'
Additional Information
Formerly known as NETIQKB1317