13:15:11
> To: users@activemq.apache.org <mailto:users@activemq.apache.org>
> Subject: Messages getting stuck on nodes without consumers, even with TTL
>
>
> Hi there!
>
>
>
> We are having some issues and need a small sanity check :')
>
>
>
> We are running a
t:
> Rest 1,2,3 produces towards a random broker 1,2,3, and service 1,2,3
> subscribes to random broker
>
> - Nikolas
>
> From: Nikolas Papaioannou <mailto:niko...@mnemonic.no.INVALID>>
> Sent: 25 October 2023 13:15:11
> To: users@activemq.apache.org <mailto:use
To: users@activemq.apache.org
Subject: Messages getting stuck on nodes without consumers, even with TTL
Hi there!
We are having some issues and need a small sanity check :')
We are running a network of brokers (multicast) with three nodes. Consumers and
producers can connect to any of
Hi there!
We are having some issues and need a small sanity check :')
We are running a network of brokers (multicast) with three nodes. Consumers and
producers can connect to any of three nodes in the network/cluster. From time
to time, we see that messages start to expire for one or more queue
We are having a problem in multiple installations of ActiveMQ where messages
are getting "stuck" in durable subscription queues. By "stuck" I mean that
the pending queue size for the subscription is greater than zero, but the
consumer never receives anything. New messages to the topic are delivered
Attached jstack trace dump of threadsl
j.lo <http://activemq.2283324.n4.nabble.com/file/n4697093/j.lo>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Re-ActiveMQ-5-11-1-JDBC-messages-getting-stuck-tp4696971p4697093.html
Sent from the ActiveMQ - User mailin
Sounds like the issue I was observing last month. ActiveMQ was randomly
deciding to just "stop" delivering messages to consumers - both the shipped
web console and hawtio showed things absolutely as I would expect them to
be.
I ended up suspending new operations, allowed existing data to be proces
though it’s entirely possible that flow control is still enabled.. maybe
the config isn’t parsed correctly. Is there a way to verify ? It isn’t in
the UI.
On Fri, Sep 19, 2014 at 5:09 PM, Kevin Burton wrote:
> - I ruled out memory issues… I tuned up memory to 3G (should be plenty)
> and enable
- I ruled out memory issues… I tuned up memory to 3G (should be plenty) and
enabled GC logging and there are no full GCs.
- I disabled producerFlowControl…
http://pastebin.com/F5L99biA
> >
> > We’re using LevelDB… the box seems to be idle while this is happening.
> >
> > There isn
Use JConsole to look at which consumers are connected (make sure at least
one is!), how many messages they're currently working on
(MessageCountAwaitingAcknowlegement), and whether the numbers appear to be
increasing. For each queue, confirm whether the EnqueueCount is
increasing; if it's not, the
We’ve been having this problem for a while now but it’s becoming more
apparent as we deploy in production.
Essentially all messages in ActiveMQ get stuck until I restart it. Today
it took three restarts… then it just started working.
Here’s my config:
http://pastebin.com/F5L99biA
We’re using L
fancy routing you can do
> with AMQ.
>
> Now that I know that, I've started some design changes to our setup to
> accommodate.
>
> Dan.
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Messages-getting-stuck-on-one-broker-tp358
Dan.
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Messages-getting-stuck-on-one-broker-tp3589529p3596741.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
---
Denis Bazhenov
FarPost.
y routing you can do
with AMQ.
Now that I know that, I've started some design changes to our setup to
accommodate.
Dan.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Messages-getting-stuck-on-one-broker-tp3589529p3596741.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
er really),
but the benefits we're expecting to see are enormous, and we're getting
really close to going live, but this is going to be a show stopper, because
we're setting too many clients stop dead because their messages aren't on
their broker :(
Thanks in advance!
Dan.
--
Vie
Hi Andy,
we also had similar problems with ActiveMQ 5.2 (see AMQ-2161).
This is apparently fixed in fuse 5.3.0.0, so we switched to fuse.
However, even with fuse, we had some additional problems, which we had to
patch ourselves (namely an out-of-memory problem and a problem with
interruptions).
w if you get anything. I'll also be trying the
>>>>> latest
>>>>> SNAPSHOT, but I don't think I can wait for long for the stable
>>>>> version.
>>>>>
>>>>> Regards,
>>>>> Vivek
>>>>&
MQ 5.0.0. I have a single enqueuer which
enqueues say
about 100 messages for a request. I have multiple (threaded)
dequeuers
running on different machines which poll Amq for messages.
After about 2k-3k messages (or probably time) I see messages
getting
stuck
in the AMQ store (I'm using pure JD
ersion.
>>>>
>>>> Regards,
>>>> Vivek
>>>>
>>>>
>>>> rajdavies wrote:
>>>>>
>>>>> Hi Vivek,
>>>>>
>>>>> this could well be a known bug - can you use 5.1 - or 5.2 (due out
well be a known bug - can you use 5.1 - or 5.2 (due out
>>>> soon)
>>>>
>>>> thanks,
>>>>
>>>> Rob
>>>> On 11 Sep 2008, at 16:31, krv wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>
>
he similar problem.
I'm using using ActiveMQ 5.0.0. I have a single enqueuer which
enqueues say
about 100 messages for a request. I have multiple (threaded)
dequeuers
running on different machines which poll Amq for messages.
After about 2k-3k messages (or probably time) I see messages
gettin
ted for the similar problem.
>>>
>>> I'm using using ActiveMQ 5.0.0. I have a single enqueuer which
>>> enqueues say
>>> about 100 messages for a request. I have multiple (threaded) dequeuers
>>> running on different machines which poll Amq for messa
y
>> about 100 messages for a request. I have multiple (threaded) dequeuers
>> running on different machines which poll Amq for messages.
>>
>> After about 2k-3k messages (or probably time) I see messages getting
>> stuck
>> in the AMQ store (I'm using pure JDBC p
iveMQ 5.0.0. I have a single enqueuer which
enqueues say
about 100 messages for a request. I have multiple (threaded) dequeuers
running on different machines which poll Amq for messages.
After about 2k-3k messages (or probably time) I see messages getting
stuck
in the AMQ store (I'm using
erent machines which poll Amq for messages.
After about 2k-3k messages (or probably time) I see messages getting stuck
in the AMQ store (I'm using pure JDBC persistence using mysql). I can see
the messages in the DB but the consumers do not get it. If I restart
ActiveMQ the messages are deliv
Yes, this is very annoying in some situations where you depend onto
this numbers. How hard / expensive (performance wise) would it be to
add an configuration flag so the numbers are actually fetched from the
message store instead of 'just' being the difference of (messages
sent)-(messages consumed)
- "eta" <[EMAIL PROTECTED]> wrote:
...
> I decided to start restart both brokers & all clients. After doing
> so, I'm
> now looking at my QueueSize in broker #1 and it's showing -1000
> messages!
...
This sounds like a known bug in ActiveMQ: ActiveMQ is unable to determine
the number of
As I posted earlier, I have a two-broker network-of-brokers configuration.
Both brokers are configured for Kaha. I just tried a test where I dumped
10K small persistent messages in quick succession onto a queue. The
consumers are just reading and throwing away the messages. All clients are
usi
28 matches
Mail list logo
