[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-users
Subject:    Re: Problem with topics
From:       artnaseef <art () artnaseef ! com>
Date:       2016-02-27 6:43:56
Message-ID: 1456555436782-4708476.post () n4 ! nabble ! com
[Download RAW message or body]

There isn't quite enough information here to be sure, but it sounds like your
hitting the slow-consumer problem.  ActiveMQ isn't a message store and
doesn't work well as such.

If producers are overloading the broker's store and/or memory, the only true
solution is to consume off those messages.

With that said, there are many patterns in which problems may occur earlier
than expected.  For example, large amounts of storage space can be consumed
by very small numbers of messages over time due to fragmentation.

So, what is the state of ActiveMQ-held messages when the broker stops
working properly?  Are there large numbers of messages stored?  Does the
broker JVM report OutOfMemory errors, or does the JVM go into GC purgatory
(i.e. spends the vast majority of its time running GC)?

BTW - bottom line with slow-consumption.  It's an anti-pattern.  Remove all
slow consumption.  Bursts (short periods of higher production than
consumption) are ok, as long as broker resources are adequately allocated to
handle them.



--
View this message in context: \
http://activemq.2283324.n4.nabble.com/Problem-with-topics-tp4708452p4708476.html Sent \
from the ActiveMQ - User mailing list archive at Nabble.com.


[prev in list] [next in list] [prev in thread] [next in thread]