activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r984765 [2/2] - in /websites/production/activemq/content: ./ cache/
Date Tue, 05 Apr 2016 03:27:19 GMT
Modified: websites/production/activemq/content/why-do-kahadb-log-files-remain-after-cleanup.html
==============================================================================
--- websites/production/activemq/content/why-do-kahadb-log-files-remain-after-cleanup.html
(original)
+++ websites/production/activemq/content/why-do-kahadb-log-files-remain-after-cleanup.html
Tue Apr  5 03:27:18 2016
@@ -43,7 +43,7 @@
       </script> 
     
     <title>
-    Apache ActiveMQ &#8482; -- Why do KahaDB log files remain after cleanup?
+    Apache ActiveMQ &#8482; -- Why do KahaDB log files remain after cleanup
     </title>
 </head>
 <body>
@@ -70,7 +70,7 @@
 <p></p>
         <div class="top_red_bar">
           <div id="site-breadcrumbs">
-<a href="community.html">Community</a>&nbsp;&gt;&nbsp;<a href="faq.html">FAQ</a>&nbsp;&gt;&nbsp;<a
href="errors.html">Errors</a>&nbsp;&gt;&nbsp;<a href="why-do-kahadb-log-files-remain-after-cleanup.html">Why
do KahaDB log files remain after cleanup?</a>
+<a href="community.html">Community</a>&nbsp;&gt;&nbsp;<a href="faq.html">FAQ</a>&nbsp;&gt;&nbsp;<a
href="errors.html">Errors</a>&nbsp;&gt;&nbsp;<a href="why-do-kahadb-log-files-remain-after-cleanup.html">Why
do KahaDB log files remain after cleanup</a>
           </div>
           <div id="site-quicklinks">
 <p><a shape="rect" href="download.html">Download</a> | <a shape="rect"
class="external-link" href="http://activemq.apache.org/maven/apidocs/index.html">JavaDocs</a>
<a shape="rect" href="javadocs.html">More...</a> | <a shape="rect" href="source.html">Source</a>
| <a shape="rect" href="discussion-forums.html">Forums</a> | <a shape="rect"
href="support.html">Support</a></p>
@@ -102,7 +102,7 @@ log4j.logger.org.apache.activemq.store.k
  TRACE | gc candidates after dest:0:J, [87] | org.apache.activemq.store.kahadb.MessageDatabase
| ActiveMQ Journal Checkpoint Worker
  TRACE | gc candidates: [87] | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ
Journal Checkpoint Worker
  DEBUG | Cleanup removing the data files: [87] | org.apache.activemq.store.kahadb.MessageDatabase
| ActiveMQ Journal Checkpoint Worker</pre>
-</div></div><p>We get one candidate, data-87.log from the existing set
of journal data files <code>[86, 87, 163, 164]</code>. There is a current transaction
using 164, destination (Queue named E) <code>'0\:E'</code> has some messages in
163, destination <code>'0:I'</code> has messages in 86 and 87 is unreferenced.
In this case, there must be some long standing unacked messages or a very slow consumer on
destination <code>'0:I'</code>.<br clear="none"> The <code>'0:'</code>
prefix is shorthand for a queue, <code>'1:'</code> for a topic, i.e: <code>dest:1:B</code>
is a topic named B.</p><p>&#160;</p><p>&#160;</p><hr><h3
id="WhydoKahaDBlogfilesremainaftercleanup?-Non-persistentmessages">Non-persistent messages</h3><p>Similar
for non-persistent messages that are not stored in your configured KahaDB persistence adapter
but get swapped to temp storage once they exceed the broker's configured memoryUsage limit.
A similar logging configuration can show details of the cleanup of temp storage
 .</p><p>&#160;</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+</div></div><p>We get one candidate, data-87.log from the existing set
of journal data files <code>[86, 87, 163, 164]</code>. There is a current transaction
using 164, destination (Queue named E) <code>'0\:E'</code> has some messages in
163, destination <code>'0:I'</code> has messages in 86 and 87 is unreferenced.
In this case, there must be some long standing unacked messages or a very slow consumer on
destination <code>'0:I'</code>.<br clear="none"> The <code>'0:'</code>
prefix is shorthand for a queue, <code>'1:'</code> for a topic, i.e: <code>dest:1:B</code>
is a topic named B.</p><p>&#160;</p><p>&#160;</p><hr><h3
id="WhydoKahaDBlogfilesremainaftercleanup-Non-persistentmessages">Non-persistent messages</h3><p>Similar
for non-persistent messages that are not stored in your configured KahaDB persistence adapter
but get swapped to temp storage once they exceed the broker's configured memoryUsage limit.
A similar logging configuration can show details of the cleanup of temp storage.
 </p><p>&#160;</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
 <pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">log4j.appender.kahadb=org.apache.log4j.RollingFileAppender
 log4j.appender.kahadb.file=${activemq.base}/data/kahadb.log
 log4j.appender.kahadb.maxFileSize=1024KB



Mime
View raw message