Document ID: TEC1816578 Last Modified Date: 03/11/2017 Show Technical Document Details
Secondary (remote) hub's baseline_engine QOS MESSAGE queue appears yellow and is backing up.
One of our secondary hubs has a queue that is backing up and not draining. As per the hub Status Tab window, its baseline_engine queue baseline_engine.QOS_MESSAGE turns yellow and doesn't send any messages.
The problem may have been caused by manual configuration during the initial hub install.
- emptying queue makes no difference- recheck of queue does nothing- baseline_engine probe security is set properly (admin *)
baseline_engine log entry:2017-01-27 15:35:07.654 [ Thread-5] INFO queuemessengerimpl.QueueReaderImpl - Queue baseline_engine.BASELINE_CONFIG is active
But note that the baseline_engine.QOS_MESSAGE queue which appears green, does NOT show any 'Id' or 'connection' info in the hub Status window and never gets a port and PID but remains green in the IM window.
After a few minutes you should see the baseline_engine.QOS_MESSAGE queue show up in the hub Queues and Status Tab windows. The queues should be green and successfully process messages.
Note that the 'bulk_size' for both queues should show their bulk_size as 1000 (this is their default out of the box bulk_size setting).
If the bulk_size was not 1000 to begin with then someone most likely manually created these queues and they will not work as expected.
They should also show an 'Id' and populate the information in the 'Established' column.