Maarten Dirkse-2 wrote:
Hi,
I've spent quite a bit of time trying to find a solution to this problem,
but nothing that I've come across in the documentation or the mailing list
seems to help, so here goes:
I've got ActiveMQ set up to provide messaging between a chain of four
To: users@activemq.apache.org
Subject: RE: Broker hitting max memory with large persistent queue
Hi Joe,
Using the Spring listeners, we've actually got about 10-20 threads on
each stage of the pipeline, all consuming messages. The problem is that
we'd like to be able to deal
An update:
I've now tried it with the standard amqpersistence config:
persistenceAdapter
amqPersistenceAdapter directory=/var/filterworks/amq/store
maxFileLength=32mb/
/persistenceAdapter
And it still results in the same problem. When I give the broker 128mb
of memory, everything
What about creating clusters of consumers for each of your processing stages
to better-handle the load spikes? The messages will get load-balanced across
the consumers in a cluster.
Joe
Get a free ActiveMQ user guide at www.ttmsolutions.com
Maarten Dirkse-2 wrote:
An update:
I've now
]
Sent: 2 mei 2008 16:22
To: users@activemq.apache.org
Subject: RE: Broker hitting max memory with large persistent queue
What about creating clusters of consumers for each of your processing
stages to better-handle the load spikes? The messages will get
load-balanced across the consumers
: Maarten Dirkse [mailto:[EMAIL PROTECTED]
Sent: 2 mei 2008 16:45
To: users@activemq.apache.org
Subject: RE: Broker hitting max memory with large persistent queue
Hi Joe,
Using the Spring listeners, we've actually got about 10-20 threads on
each stage of the pipeline, all consuming messages
