uot;
> p:targetConnectionFactory-ref="jmsFactory" />
>
>p:receiveTimeout="${jms.receivetimeout}" p:connectionFactory-ref="scf" />
>
> id="commandTemplate" p:receiveTimeout="${jms.receivetimeout}"
> p:explicitQosEnabled="true"
> p:priority="4" p:deliveryMode="2" p:timeToLive="12"
> p:connectionFactory-ref="scf" p:defaultDestination-ref="commandTopic" />
>
>
>
>
>
>
>
>
> Thanks in advance,
> Maarten
>
>
>
>
--
View this message in context:
http://www.nabble.com/Broker-hitting-max-memory-with-large-persistent-queue-tp17014805s2354p17606223.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
From: 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
> eac
ssage-
From: 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 con
[mailto:[EMAIL PROTECTED]
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
tion.SingleConnectionFactory"
> p:targetConnectionFactory-ref="jmsFactory" />
>
> id="jmsTemplate" p:receiveTimeout="${jms.receivetimeout}"
> p:connectionFactory-ref="scf" />
>
>id="commandTemplate" p:receiveTimeout="${jms.receivetimeout}"
> p:explicitQosEnabled="true"
> p:priority="4" p:deliveryMode="2" p:timeToLive="12"
> p:connectionFactory-ref="scf" p:defaultDestination-ref="commandTopic" />
>
>
>
>
>
>
>
> Thanks in advance,
> Maarten
>
>
>
>
--
View this message in context:
http://www.nabble.com/Broker-hitting-max-memory-with-large-persistent-queue-tp17014805s2354p17020505.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
to a
crawl.
Anyone have any ideas as to what's going on?
Regards,
Maarten
-Original Message-
From: Maarten Dirkse [mailto:[EMAIL PROTECTED]
Sent: 2 mei 2008 9:02
To: users@activemq.apache.org
Subject: Broker hitting max memory with large persistent queue
Hi,
I've spent quit
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
components, connected by three queues like
