Problem with topics

[jcascantem <jp...@gmail.com>]

Hi.


I have a system that use ACtiveMQ to split information through topics to
many client applications, but the problem is that if an client app is
disconnected, the other queues (topics) stop working, because Active MQ is
not able to manage the information queued.



you have an idea about how to solve this problem ?? How can I do to avoid
that ActiveMQ stop woking when an consumer is not connected?


Best Regards.


JPC



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

Re: Problem with topics

[artnaseef <ar...@artnaseef.com>]

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.