We had this issue with qpid ++ broker and was related to vectors used in
long running objects (queues etc) c++11 introduced shrink_to_fit() and we
patched the broker at that time to avoid those memory issues.
On Fri, 15 Dec 2023 at 18:21 Ekta Awasthi
wrote:
> Hello Tod,
>
> while running the qds
Hello Tod,
while running the qdstat -m command, I get below error.
-sh-4.2$ qdstat -a
ConnectionException: Connection amqp://0.0.0.0:amqp disconnected:
Condition('proton.pythonio', 'Connection refused to all addresses')
Ekta Awasthi,
Engineer, EAI Operations & Support | Office Depot, Inc.
6
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
Hi All & Tod,
We are currently encountering elevated memory consumption with qpid dispatch
version 1.19.0. Although the memory is released upon restarting qpid, it
gradually accumulates again, surpassing 80% memory usage. As QPID in our case
servers as a routing mechanism, handling traffic from
Thank you!
On Fri, Dec 15, 2023 at 1:43 AM Robbie Gemmell
wrote:
> We dont keep a specific 'EOL details' so I can't refer you to any,
> even if you had indicated which you are interested in.
>
> Essentially if a version isnt on the website as a current release it
> is definitely EOL, though bein
We dont keep a specific 'EOL details' so I can't refer you to any,
even if you had indicated which you are interested in.
Essentially if a version isnt on the website as a current release it
is definitely EOL, though being on the website doesn't mean it isnt
also effectively so, e.g the cpp broker
