something does not make sense.
Attach queues do not send messages, they only collect messages.
Get queues to retrieve messages.
If the get queue can not connect to the attach queue you should have gotten an alarm.
is the connection down or did is slow down?
The hub has a built-in mechanism where it will try to collect the number of messages set in the bulk size. Byt default 100 messages.
If this fails or times out due to latency or low bandwidth the hub will start reducing the bulk size until it gets to 1.
Once it reaches 1 currently the only way to reset it is to restart the hub.
The first thing to address would be any high latency issues or low bandwidth connections between the hub. you can do a transfer check between the hubs on the hub screen. this value should be well above 300 kbs
Once that is done make sure you have applied the below two KB articles to all hubs and controllers on hubs.
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=72187https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=10838------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 02-19-2020 10:31 AM
From: Keith Clay
Subject: Get queue status
Folks,
We have customer hubs where the attach queues stop sending to the get queues on secondary hubs. How can we watch those queues to see if they are down? We've had a couple situation where we check the customer hub and the queues have over a million items that weren't sent.