activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruce Snyder <bruce.sny...@gmail.com>
Subject Re: ActiveMQ 5.3.0 cpu usage goes to zero
Date Mon, 29 Mar 2010 19:17:42 GMT
On Mon, Mar 29, 2010 at 3:20 PM, TMcCabe <team_mc@hotmail.com> wrote:
>
> More  information.....
>
> VM Summary physical memory goes way down to 150,516.
> So the resource thing might be right.
>
> Heap usage for AMQ seems excellent.
>
> Do I have the correct configuration for AMQ to store persistent msgs to
> disk?


>>         <persistenceAdapter>
>>             <amqPersistenceAdapter
>> directory="${activemq.base}/data/activemq-data" syncOnWrite="false" />
>>         </persistenceAdapter>

Well, as shown above, the AMQ persistence adapter is configured for
the possibility of persistent messages. But persistent messaging is
not determined by the broker, it's determined by the producer who
sends the message. A message must be marked persistent if you want it
to be stored in a persistent store. This takes place via the JMS API
for the MessageProducer object, specifically the setDeliveryMode
method:

http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html#setDeliveryMode(int)

Bruce
-- 
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'

ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder

Mime
View raw message