activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <>
Subject Re: Consumer queues for virtual topics do not receive messages
Date Wed, 24 Jul 2013 04:25:56 GMT
I have an idea about what is happening.. your queues are probably caching
messages which contribute to the  memory limit and periodically your topic
subscriptions are thinking memory is full (which it is.. it can be above
100% when producer flow control is off..)... so even though PFC is turned
off for topics, the topic subscriptions still check for memory usage when
adding to the topic subscription's dispatch queue.

If you post your complete config, and if I get more cycles, I can validate
that hypothesis. An even quicker approach for both of us would be if you
write a unit test that shows your usecase and reproduce the log messages
you're getting about the TopicSubscription being full.

On Tue, Jul 23, 2013 at 1:41 AM, rsteppac <> wrote:

> Yes, I have a subscriber per advisory topic on the server. I am not using
> the
> scheduler (not knowingly anyways).
> I thought the log output might be related because we see messages sent to
> the topic occasionally never hit some subscribers; at the same time the
> MBean for the subscriber queue shows a small amount of expired messages.
> That the two effects, missing a beat and message expiration, are related is
> just an assumption so far...
> The producers and consumers are all started through Camel using the
> ActiveMQ
> compoment. Does that answer your question about the kind of
> producers/consumers?
> In production we deal with about 60 million messages over a 12hour business
> day. The size of the high volume messages is about 2.5kb. We have some low
> volume messages (the ones put on the virtual topics) where the sizes range
> between 1 and 10kb.
> Ralf
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

*Christian Posta*
twitter: @christianposta

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message