svn commit: r872357 - in /websites/production/activemq/content: cache/main.pageCache kahadb.html

[bu...@apache.org]

Author: buildbot
Date: Thu Aug  1 21:23:09 2013
New Revision: 872357

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/kahadb.html

Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/activemq/content/kahadb.html
==============================================================================
--- websites/production/activemq/content/kahadb.html (original)
+++ websites/production/activemq/content/kahadb.html Thu Aug  1 21:23:09 2013
@@ -80,7 +80,7 @@
 <p>You can configure ActiveMQ to use KahaDB for its persistence adapter - like below :</p>
 
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
  
  &lt;broker brokerName="broker" ... &gt;
     &lt;persistenceAdapter&gt;
@@ -112,10 +112,8 @@ If database operation is slower than tha
 
 <p>You can configure a threshold used to log these messages by using a system property and adjust it to your disk speed so that you can easily pick up runtime anomalies.</p>
 
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
--Dorg.apache.activemq.store.kahadb.LOG_SLOW_ACCESS_TIME=1500
-]]></script>
+<div class="panel" style="border-width: 1px;"><div class="panelContent">
+<p>-Dorg.apache.activemq.store.kahadb.LOG_SLOW_ACCESS_TIME=1500</p>
 </div></div>
 
 <h1><a shape="rect" name="KahaDB-Multi%28m%29kahaDBpersistenceadapter"></a>Multi(m) kahaDB persistence adapter</h1>
@@ -128,7 +126,7 @@ In these cases you can use the mKahaDB p
 <h2><a shape="rect" name="KahaDB-Configuration"></a>Configuration</h2>
 <p>Each instance of kahaDB can be configured independently. If no destination is supplied to a <tt>filteredKahaDB</tt>, the implicit default value will match any destination, queue or topic. This is a handy catch all. If no matching persistence adapter can be found, destination creation will fail with an exception. The <tt>filteredKahaDB</tt> shares its wildcard matching rules with <a shape="rect" href="per-destination-policies.html" title="Per Destination Policies">Per Destination Policies</a>.</p>
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;broker brokerName="broker" ... &gt;
  &lt;persistenceAdapter&gt;
   &lt;mKahaDB directory="${activemq.base}/data/kahadb"&gt;
@@ -157,7 +155,7 @@ In these cases you can use the mKahaDB p
 <h3><a shape="rect" name="KahaDB-Automaticperdestinationpersistenceadapter"></a>Automatic per destination persistence adapter</h3>
 <p>When the <tt>perDestination</tt> boolean attribute is set to true on the catch all (no explicit destination set), <tt>filteredKahaDB</tt>. Each matching destination will get its own <tt>kahaDB</tt> instance.</p>
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;broker brokerName="broker" ... &gt;
  &lt;persistenceAdapter&gt;
   &lt;mKahaDB directory="${activemq.base}/data/kahadb"&gt;