Tech Tip: UIM - Secondary (remote) hub's baseline_engine QOS MESSAGE queue turned yellow and is backing up

Document created by danst04 Employee on Mar 13, 2017
Version 1Show Document
  • View in full screen mode

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.

- UIM v8.4 - baseline_engine 2.76 - prediction_engine 1.34 - hub_780HF22 - robot_update 7.80HF21

The problem may have been caused by manual configuration during the initial hub install.

  1. Deactivate the baseline_engine probe on the remote hub
  2. Delete both baseline_engine queues (baseline_engine.QOS_MESSAGE and baseline_engine.BASELINE_CONFIG) via the hub GUI Queues Tab window and click Apply
  3. Activate baseline_engine (Note that the baseline_engine.BASELINE_CONFIG is created automatically and does not need to be created/recreated manually). Check to be sure its created via the hub Status Tab window.
  4. Then use the web Admin Console to configure a simple baseline for a probe on one of the robots off of that same hub. Once a baseline is created by checking the 'Compute Baseline' checkbox then clicking 'Save,' it creates a baseline QOS message and then the baseline_engine.QOS_MESSAGE queue is created automatically - it also does NOT need to be created/recreated manually.




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.

4 people found this helpful