ed Count 273624
>
> Modified Count 962
>
> Deliveries Delayed > 1sec4901525
>
> Deliveries Delayed > 10sec 775262
>
> Deliveries Stuck > 10sec 0
>
> Deliveries to Fallback 0
>
>
48
Deliveries to Route Container32649333
Thanks,
Nilesh Khokale
From: Virgilio Fornazin
Sent: Friday, December 15, 2023 4:23 PM
To: users@qpid.apache.org
Cc: Ajit Tathawade (Contractor) ; Nilesh Khokale
(Contractor) ; Ted Ross
Subject: Re: High Memory consumption with Qpid Dispatch 1.19.0
[CA
minder, the Service Availability Managers should be engaged for
> any service impacting issues, with a ***Page*** to
> naitavailabilitym...@officedepot.com or by initiating a MIRT
> --
> *From:* Ted Ross
> *Sent:* Friday, December 15, 2023 2:48 PM
> *To:* Ekta Awasthi
sers@qpid.apache.org ; Ajit Tathawade (Contractor)
; Nilesh Khokale (Contractor)
Subject: Re: High Memory consumption with Qpid Dispatch 1.19.0
[CAUTION: EXTERNAL SENDER]
Ekta,
You can get more granular memory-use data by using the "qdstat -m" command
against the router when its memo
Ekta,
You can get more granular memory-use data by using the "qdstat -m" command
against the router when its memory footprint is larger than you think it
should be.
I assume you've been using this version for some time. It might be helpful
to look into what other things changed right before the
