On 6/12/07, Arif Mohd <[EMAIL PROTECTED]> wrote:
Hi Gert,
1) If i move from derby to mysql, How will be the internal working of
durable topic and queues?
I assume you're referring to changing the persistence configuration
for ActiveMQ, correct? If this is what you're referring to, the only
thing that this affects is that messages are persisted to MySQL
instead of Derby. The big advantage to doing this is that Derby can be
very garbage collection intense under heavier loads. So using a
database that does not run in the same JVM as ActiveMQ can improve the
performance of the JVM therefore freeing up resources.
2) Does the messages stored in DB(messages of durable topic and queues)
will be loaded into memory as and when they are required? or all the
messages from the DB will be loaded into heap?
I assume you're using ServiceMix 3.1 which uses ActiveMQ 4.1. This
version of ActiveMQ holds all messages in memory and is therefore
limited to the amount of memory available. (As a side note, ActiveMQ
5.0 (the trunk) can now spool messages to disk and does so by default.
This allows ActiveMQ to scale much further regarding the number of
messages it can handle.)
3) will it work like Paging concept of Operating system?
See above, this functionality is available in ActiveMQ 5.0 (the trunk).
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
