How are your consumers setup? This looks like a mesh config.. I'm
wondering if the max message hop ttl was reached and the messages are
parked in that one broker. That scenarios is helped by splitting the
consumerTTL and the messageTTL and not using networkTTL.
Do you have a specific reason for not setting conduitSubscriptions=true?
<networkConnector name="linkToBroker1"
uri="static:(tcp://c01-meq1:61616)"
networkTTL="3"
conduitSubscriptions="false" />
<networkConnector name="linkToBroker2"
uri="static:(tcp://c01-meq2:61616)"
networkTTL="3"
conduitSubscriptions="false" />
On 9/14/16 10:01 PM, Geoffrey Mina wrote:
Greetings,
I am pretty new to ActiveMQ as we just deployed into our stack.
We had a network of brokers have a significant problem tonight due to
(what appeared to be) a single broker. 2 of the 3 were processing
messages OK and the third was queuing up and not processing messages
quickly. This is for a real-time application and seconds (even
milliseconds) count.
There was absolutely nothing in the log file that was interesting.
I even restarted the “bad” broker and when it came back online it was
behaving identically. We have persistence completely disabled and
there is not even a kahadb on the file system.
I have attached my config here for one of the brokers (all configs
identical except for the the network config). If anyone sees anything
glaringly obvious, please let me know. We just deployed this cluster
of servers last Friday. It has processed hundreds of millions of
messages in the last few days – before it began to misbehave tonight.
ActiveMQ 5.14.0
java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
Amazon EC2 Host
CentOS 7
3.10.0-327.10.1.el7.x86_64
4 x Intel(R) Xeon(R) CPU E5-2666 v3 @ 2.90GHz
8G RAM
Thanks in advance!
Geoff
