Author: buildbot
Date: Tue Apr 30 16:21:35 2013
New Revision: 860403
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/persistence.html
Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/activemq/content/persistence.html
==============================================================================
--- websites/production/activemq/content/persistence.html (original)
+++ websites/production/activemq/content/persistence.html Tue Apr 30 16:21:35
2013
@@ -76,8 +76,9 @@
<p>From 5.3 onwards - we recommend you use <a shape="rect" href="kahadb.html"
title="KahaDB">KahaDB</a> - which offers improved scalability and
recoverability over the <a shape="rect" href="amq-message-store.html"
title="AMQ Message Store">AMQ Message Store</a>.</p>
-<p>The <a shape="rect" href="amq-message-store.html" title="AMQ Message
Store">AMQ Message Store</a> which although faster than <a shape="rect"
href="kahadb.html" title="KahaDB">KahaDB</a> - does not scales as well as <a
shape="rect" href="kahadb.html" title="KahaDB">KahaDB</a> and recovery times
take longer.</p>
+<p>In ActiveMQ 5.8, the <a shape="rect" href="leveldb-store.html"
title="LevelDB Store">LevelDB Store</a> was introduced. Although not yet the
default message store, it provides better performance than <a shape="rect"
href="kahadb.html" title="KahaDB">KahaDB</a>. We expect this store
implementation become the default in future releases.</p>
+<p>The <a shape="rect" href="amq-message-store.html" title="AMQ Message
Store">AMQ Message Store</a> which although faster than <a shape="rect"
href="kahadb.html" title="KahaDB">KahaDB</a> - does not scales as well as <a
shape="rect" href="kahadb.html" title="KahaDB">KahaDB</a> and recovery times
take longer.</p>
<h2><a shape="rect" name="Persistence-ActiveMQV4"></a>ActiveMQ V4</h2>
<p>For long term persistence we recommend using JDBC coupled with our high
performance journal. You can use just JDBC if you wish but its quite slow.</p>
