activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: Force JDBC persistence
Date Thu, 01 Feb 2007 13:41:18 GMT
This question was answered in the other thread you raised

http://www.nabble.com/Re%3A-JDBC-persistance-in-AMQ-4.1.0-p8718202.html


On 1/30/07, Nilantha <Nilantha.Jayalath@autodata.net> wrote:
>
> I am testing JDBC persistence with one broker and my "persistenceAdapter'
> configuration is as follows,
>     <persistenceAdapter>
>
>       <journaledJDBC journalLogFiles="5"  dataSource="#oracle-ds"/>
>
>     </persistenceAdapter>
>
> I have noticed following at one point When I sent some 50000 messages
> without consuming.
>
> No of messages in DB( in "ACTIVEMQ_MSGS"): 43764
> Total in queue: 51128 (through Jconsole)
>
> After some time all the messages were available in DB. It appears that
> broker keeps messages in memory until it close to allowable memory limit and
> then flush into the DB(more than 10k some times depend on the message size
> ). Is there a way I could force DB persistence without keeping messages in
> memory.
>
> My concern is in case of a hardware failure those in memory message could be
> lost?
>
> Thanks in advance for any idea on this..
>
> --
> View this message in context: http://www.nabble.com/Force-JDBC-persistence-tf3142318.html#a8709190
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message