Hello Ted,
Thank you for your response.
We are using AutoLinks for our addresses. Below is an example of a autolink
queue in qdrouterd.conf for one activemq broker pair. Thanks
address {
prefix: test-queue
waypoint: yes
}
autoLink {
connection: od-broker-1-m
addr: test-queue
dir: in
}
autoLink {
connection: od-broker-1-m
addr: test-queue
dir: out
}
autoLink {
connection: od-broker-1-s
addr: test-queue
dir: in
}
autoLink {
connection: od-broker-1-s
addr: test-queue
dir: out
}
Ekta Awasthi,
________________________________
From: Ted Ross <tr...@redhat.com>
Sent: Tuesday, January 3, 2023 8:47 AM
To: users@qpid.apache.org <users@qpid.apache.org>
Cc: Ajit Tathawade (CompuCom) <ajit.tathaw...@officedepot.com>; Nilesh Khokale
(Contractor) <nilesh.khok...@officedepot.com>; EAIOpsSupport
<eaiopssupp...@officedepot.com>
Subject: Re: More than configured consumers count
[CAUTION: EXTERNAL SENDER]
Hi Etka,
Can you tell us how you have configured the qdrouters to act as consumers? Are
you using auto-links or are you using link-routed addresses?
-Ted
On Wed, Dec 28, 2022 at 11:20 AM Ekta Awasthi
<ekta.awas...@theodpcorp.com.invalid> wrote:
Hello,
Is this the right mailing DL for QPID related queries.
Just wondering as I have not heard back but given it is a holiday season, so I
will sit back and wait patiently for someone to reply.
Thanks In Advance.
Ekta Awasthi
________________________________
From: Ekta Awasthi
<ekta.awas...@theodpcorp.com<mailto:ekta.awas...@theodpcorp.com>>
Sent: Thursday, December 22, 2022 1:00 AM
To: users@qpid.apache.org<mailto:users@qpid.apache.org>
<users@qpid.apache.org<mailto:users@qpid.apache.org>>
Cc: Ajit Tathawade (CompuCom) <ajit.tathaw...@officedepot.com>; Nilesh Khokale
(Contractor) <nilesh.khok...@officedepot.com>; EAIOpsSupport
<eaiopssupp...@officedepot.com<mailto:eaiopssupp...@officedepot.com>>
Subject: More than configured consumers count
Hi There,
We have few issues with the qpid-dispatch router where we are seeing multiple
consumers are getting created randomly by our qpid dispatch routers. We are
unable to trace nor able to replicate this issue in our lower env's. Below is
the architecture diagram.
I apologize if this isn't the right place to ask this question. In case there
is another place to communicate, do let me know as this is my first time
reaching out regarding qpid query😀 Please provide any suggestions or feedback
to help us understand this issue better. Thanks
Flow:
Microservice (Kubernetes) ---> NLB (Load balancer) ---> 2 Qpid-Dispatch Routers
acting up as consumers in front of brokers (1.16 version) ---> 4 Broker pairs
of activemq(2.18 version) masters and slaves (independent pairs)
Problem statement # 1
We are seeing more than the configured number of consumers count in our
activemq hawtio console causing messages to sit in delivering count which are
Un browsable since those messages are currently being delivered to its
consumers. Having only two qpid dispatch routers(acting as consumers) infront
of our activemq brokers, the count should always remain 2 but at times it is
going 3 sometimes 4. To resolve this issue, we are having to bounce the qpid’s
to release the stuck/bad consumer so that messages can be processed/consumed.
Problem statement # 2
At times we see messages going to delivering count even when there are only two
configured consumers(2qpids) showing in activemq hawtio console. We don't know
the cause to why the messages get stuck in delivering count. To resolve this,
we tried restarting the consumer service but that did not help. Next up we
tried restarting the brokers, that did not help and noticed that all the stuck
delivering messages, the broker slowly replayed back and Eventually the stuck
messages came back to delivering count post broker restart. To resolve this
issue, we are having to bounce the qpid’s to release the messages and that
fixes the issue.
Version of qpid-dispatch router
qpid-dispatch-router-1.16.0-1.el7.x86_64.rpm
qpid-dispatch-tools-1.16.0-1.el7.noarch.rpm
Ekta Awasthi
CONFIDENTIALITY NOTICE: The information contained in this email and attached
document(s) may contain confidential information that is intended only for the
addressee(s). If you are not the intended recipient, you are hereby advised
that any disclosure, copying, distribution or the taking of any action in
reliance upon the information is prohibited. If you have received this email in
error, please immediately notify the sender and delete it from your system.
